-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
No "prompt" param in oidc connection URL even when "promptType" is set #3740
Comments
It only works with the offline access scope. See Lines 352 to 355 in 20f240c
|
Is there plan to extend this? Not sure what the design principle is behind this. |
I also noticed this issue. I also wonder if it is a design issue. |
It seems like the value was once hardcoded and then unhardcoded It doesn't look like a deep design decision too me, so we can fix this> ? Will it be a breaking change? |
Preflight Checklist
Version
2.41.1
Storage Type
Kubernetes
Installation Type
Official Helm chart
Expected Behavior
Using oidc connector, with
connector.config.promptType=fido2
, I expect dex would appendprompt=fido2
in the URL while calling the backend OIDC provider, but observed that noprompt
param exist in the request URLActual Behavior
request URL should have
prompt=fido2
in/oauth/authorize
call against backend OIDC providerSteps To Reproduce
Additional Information
No response
Configuration
Logs
dex app log shows nothing
ingress log for dex
ingress log for backend oidc provider
Notice there's no "prompt" parameter in the
/oauth/authorize
callThe text was updated successfully, but these errors were encountered: