Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

no X-Userinfo and X-Access-Token #24

Open
salahberiani opened this issue Oct 23, 2022 · 0 comments
Open

no X-Userinfo and X-Access-Token #24

salahberiani opened this issue Oct 23, 2022 · 0 comments

Comments

@salahberiani
Copy link

salahberiani commented Oct 23, 2022

i only get session cookie in my app i dont get x-userinfo and x-access-token
and that the oicd config

{
	"next": null,
	"data": [
		{
			"id": "ebff355a-ecdc-41b3-a240-d42f08a3b6c2",
			"protocols": [
				"grpc",
				"grpcs",
				"http",
				"https"
			],
			"enabled": true,
			"config": {
				"groups_claim": "groups",
				"header_names": [],
				"header_claims": [],
				"disable_userinfo_header": "no",
				"userinfo_header_name": "X-USERINFO",
				"ssl_verify": "no",
				"revoke_tokens_on_logout": "no",
				"disable_access_token_header": "no",
				"access_token_as_bearer": "no",
				"disable_id_token_header": "no",
				"id_token_header_name": "X-ID-Token",
				"unauth_action": "auth",
				"recovery_page_path": null,
				"bearer_only": "no",
				"use_jwks": "no",
				"client_secret": "dbBPlZ2gm2oVIaZ8Gtijr9RcMY9xrDo4",
				"introspection_endpoint_auth_method": null,
				"introspection_cache_ignore": "no",
				"redirect_uri": null,
				"response_type": "code",
				"scope": "openid",
				"ignore_auth_filters": "",
				"logout_path": "/logout",
				"redirect_after_logout_uri": "https://host:8180/auth/realms/kong/protocol/openid-connect/logout?redirect_uri=https://146.59.240.225",
				"discovery": "http://host:8180/realms/kong/.well-known/openid-configuration",
				"bearer_jwt_auth_allowed_auds": null,
				"timeout": null,
				"client_id": "kong-oicd",
				"session_secret": null,
				"skip_already_auth_requests": "no",
				"bearer_jwt_auth_signing_algs": [
					"RS256"
				],
				"access_token_header_name": "X-Access-Token",
				"token_endpoint_auth_method": "client_secret_post",
				"bearer_jwt_auth_enable": "no",
				"realm": "kong",
				"filters": null,
				"introspection_endpoint": "http://host:8180/auth/realms/kong/protocol/openid-connect/token/introspect"
			},
			"tags": null,
			"created_at": 1666421915,
			"route": null,
			"consumer": null,
			"name": "oidc",
			"service": null
		}
	]
}

and my goal is to get the current logged in user in my backend for some required logic dose this mean when i send request from my app to my api the x-userinfo and X-Access-Token will be available in the request header ?

using keycloack 19.0.3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant