Open yacman opened 9 months ago
Same issue here - any fixes?
Facing the same problem with Keycloak + K8s 1.28 I have not found any workaround to this
same problem here, is there any solution to this?
same problem here, is there any solution to this?
I have just switched to Headlamp :)
I tried to switch to Headlamp, but my developers said - It’s a nuisance
I have the same problem, need help.
@bmgeek
It was easy to use for us :)
But you can fork and fix the PR if you are interested then use your port
Encountered the same issue! Any solution?
Utilizing keycloak version
23.0.4
which contains a realm with multiple clients where one or more containauthorization_response_iss_parameter_supported=true
, this value will always be true for the /.well-known/openid-configuration.https://github.com/keycloak/keycloak/issues/25419
Given this, when the
node-openid-client
is hydrated by this endpoint, the following validation takes place and throws:https://github.com/panva/node-openid-client/blob/main/lib/client.js#L437
Reviewing the auth flow for Skooner it is declaring specific keys to proxy when submitting /oidc requests where the issuer is also required.
https://github.com/skooner-k8s/skooner/blob/master/client/src/services/api.ts#L122 https://github.com/skooner-k8s/skooner/blob/master/server/index.js#L145
These endpoints should, when supplied, also proxy the
iss
parameter. When theiss
parameter is provided and valid, the 500 is corrected.