-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keycloak no id_token #41
Comments
@omario36 , what is the config you are using? |
@omario36, try setting the following in your provider config.
|
|
This is our config maybe it helps you.
|
@omario36 You got "realm master" we have "realm keycloak" try to change that? |
@axi92 ok I will try to create a new realm "keycloak" and will keep you informed, many thanks |
@axi92 thank you now Its ok for the token I have : But now I have something like an infinite login loop with this test url : |
The scopes should not matter, as you give every user that comes from keycloak the authp/user
And you allow in your policy: |
I don't know if this config is valid:
You don't need to check the /whoami endpoint, authp denies access to that endpoint if you dont have a valid session. So no need to have that config IMHO. You should see the Whoami endpoint on the linklist after the login is successful. |
@axi92 sorry but here whoami is the service that I want to secure buy keycloak oauth The new config is :
Thanks for your support, I realy need to secure for example this whoami or another service proxied by the caddy. |
maybe because the domain of my keycloak auth and the whoami service is different ? so AUTHP_SESSION_ID cookie is rejected ? |
@greenpau any link to update the documentation for using keycloak v20 + ? |
Hello
Using the latest version of keycloak 20.x
my jwt token looks like :
{ "exp": 1670518964, "iat": 1670518904, "auth_time": 1670518904, "jti": "5ec29444-3409-4d6a-8999-c442a1942e0b", "iss": "https://#######/realms/master", "sub": "131d20a2-79d4-40ec-9e65-e4baaa488145", "typ": "Bearer", "azp": "test-caddy", "nonce": "N2giK5dZPbxpgivEMMvE50l0afvGUK00", "session_state": "e755a31c-12bd-4bb6-829a-9afe4cad4772", "scope": "profile email", "sid": "e755a31c-12bd-4bb6-829a-9afe4cad4772", "email_verified": true, "name": "Omar Omari", "groups": [ "authp/admin", "default-roles-master", "authp/user", "authp/guest", "offline_access", "uma_authorization" ], "preferred_username": "oomari", "given_name": "Omar", "family_name": "Omari", "email": "########" }
I have this error
{"level":"debug","ts":1670518426.718966,"logger":"security","msg":"failed fetching OAuth 2.0 access token from the authorization server","session_id":"L4qZa6GSvpwfxej0lrPgQ0AshlmISYR20O2dm86l","request_id":"e0a6d25f-b162-4ce0-a175-483db6900fdb","error":"authorization server response has no \"id_token\" field"}
The text was updated successfully, but these errors were encountered: