-
Notifications
You must be signed in to change notification settings - Fork 75
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
feat [auth-server]: Device Flow needs configurable acr #4305
Labels
comp-jans-tui
kind-bug
Issue or PR is a bug in existing functionality
kind-feature
Issue or PR is a new feature request
Milestone
Comments
It was already reported and fixed in 1.0.11 #4278 |
Re-opening and assinging to @devrimyatar to check whether cli sets default acr correctly. |
yuriyz
changed the title
fix(jans-auth): auto 2fa enabling if once fido2/super_gluu scripts are enabled
fix(tui): auto 2fa enabling if once fido2/super_gluu scripts are enabled
Mar 25, 2023
nynymike
changed the title
fix(tui): auto 2fa enabling if once fido2/super_gluu scripts are enabled
feat [auth-server]: Device Flow needs configurable acr
Mar 25, 2023
I repaced the original content of this message with the root cause--there is no way in Auth Server to specify the acr for device flow. |
yuriyz
added a commit
that referenced
this issue
Apr 3, 2023
2 tasks
yuriyz
added a commit
that referenced
this issue
Apr 3, 2023
This was referenced Apr 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
comp-jans-tui
kind-bug
Issue or PR is a bug in existing functionality
kind-feature
Issue or PR is a new feature request
We need a way to specify the acr (and potentially other params, like
agama_flow=...
) for device flow. Otherwise when you enable two acr's, it's unpredictable which one may run. Perhaps we can add two Auth Server configuration JSON properties :device_flow_default_acr
anddevice_flow_extra_authn_params
?The text was updated successfully, but these errors were encountered: