Client error on keycloak token endpoint

I tried to integrate django with keycloak openid by using this library. Unfortunately I got this message

400 Client Error: Bad Request for url: http://KEYCLOAK-IP/auth/realms/myrealm/protocol/openid-connect/token

Here is my sample settings in my django application

OIDC_RP_SIGN_ALGO = 'RS256'

OIDC_OP_JWKS_ENDPOINT = 'http://KEYCLOAK-IP/auth/realms/myrealm/protocol/openid-connect/certs'

OIDC_RP_CLIENT_ID = 'webapp'
OIDC_RP_CLIENT_SECRET = '29357c72-ed21-4a4c-a882-58194b63cb1f'


OIDC_OP_AUTHORIZATION_ENDPOINT = 'http://KEYCLOAK-IP/auth/realms/myrealm/protocol/openid-connect/auth'

OIDC_OP_TOKEN_ENDPOINT = 'http://KEYCLOAK-IP/auth/realms/myrealm/protocol/openid-connect/token'

OIDC_OP_USER_ENDPOINT = 'http://KEYCLOAK-IP/auth/realms/myrealm/protocol/openid-connect/userinfo'

I would be glad if someone could help me with this issue 😃.

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:10 (1 by maintainers)

Top GitHub Comments

4reactions

airen29commented, Dec 2, 2020

I’ve got a similar problem. Error was: Keycloak returns HTTP-400 "error":"invalid_grant","error_description":"Code not valid" I’ve solved this problem by setting Access Token Lifespan to higher numbers.

Then I’ve encoutered the problem, that Keycloak endpoint /token was on first attempt returning 200 OK but didn’t respond with access_token. On second attempt I’ve got 400 HTTP error. I’ve solved this problem thanks to adding * into web origin in Keycloak settings.

I hope this answer helps someone.

2reactions

surfer190commented, Nov 4, 2019

If you go to:

http://KEYCLOAK-IP/auth/realms/{realm}/.well-known/openid-configuration

All the endpoints are given. I’m testing this now though and will get back to you.