This repository has been archived by the owner on Dec 7, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 345
old github.com/coreos/go-oidc #514
Comments
|
There is "standard" workaround to configure mapper, which will generate correct aud in the Keycloak - https://stackoverflow.com/questions/53550321/keycloak-gatekeeper-aud-claim-and-client-id-do-not-match Migration to v2 will take a time, but it is on the radar - #407 (comment) |
the workaround configuration works, thanks :) Lets me get to the next failure i need to work through - figuring how best to hack in x-forward generation of redirect_uri :D |
Hi @SvenDowideit I'm closing it because it will be superseded by #517. Please, add any comments there if you find more issues with go-oidc. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
So I was having some issues with moving a slightly hacked keycloak v4.0.5 to v9.0.2, and one thing that is hitting me, is that the token aud != the clientid - but the azp does
which then lead me to realise that the github.com/coreos/go-oidc module has a v2, and they're talking about a v3 - and that the code we're using is from 2017
I have a small change to github.com/coreos/go-oidc that seems to get me further
So i'm wondering if there's any advice - should I fork the old go-oidc, and build with that for now, or is this something that's on the radar already, and updating to v2 won't be an issue, or ?
The text was updated successfully, but these errors were encountered: