-
Notifications
You must be signed in to change notification settings - Fork 170
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
JWS token verification failed.... even with HS256 set and no other token provider in Keycloak. #382
Comments
I could move forward by replacing the token key by the JWT endpoint ... but then fails with the other defect I opened. |
@strus38 any extra information why HS256 doesn't work? |
I think the user info is not decoded cf the code.
Le ven. 20 nov. 2020 à 16:56, Pedro Mendes <[email protected]> a
écrit :
… @strus38 <https://github.com/strus38> any extra information why HS256
doesn't work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#382 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABM6DUZMJWWQ5MRVUJPESCTSQ2GRTANCNFSM4TFDUPCA>
.
|
I was having the same problem with HS256, then I changed to RS256 and define the OIDC_RP_SIGN_ALGO = 'RS256'
OIDC_OP_JWKS_ENDPOINT = 'https://keycloak-dev/auth/realms/test/protocol/openid-connect/certs' |
I'm having the same problem with HS256 (JWS token verification failed), but when changing to RS256 and define OIDC_OP_JWKS_ENDPOINT to ../certs, I get an json parser exception.. see #421 |
It might be a key format issue, see #505 (comment) (I had a similar issue and now have a working setup with keycloak). |
Hi
I am deploying Netbox on K8S and I am trying to add OIDC with keycloak to allow SSO on Netbox.
So I have done the necessary changes - I guess - but failing on JWT issue even of HS256 is the only token provider on Keycloak!
Error: JWS token verification failed.
By the way: OIDC_VERIFY_JWT does not seem to to do anything!
Removing OIDC_OP_JWKS_ENDPOINT does not work either
The text was updated successfully, but these errors were encountered: