-
Notifications
You must be signed in to change notification settings - Fork 79
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(jans-auth-server): allow invoke consent script by acr #10548
Milestone
Comments
From #10686 (comment) What if we add another configuration property that has mapping acr to consent flow like this
Algorithm is :
It means we will need two additional configuration mappings. |
yuriyz
added a commit
that referenced
this issue
Jan 21, 2025
Signed-off-by: YuriyZ <[email protected]>
4 tasks
yuriyz
added a commit
that referenced
this issue
Jan 29, 2025
…0712) * feat(jans-auth-server): allow invoke consent script by acr #10548 Signed-off-by: YuriyZ <[email protected]> * added consent script identification Signed-off-by: YuriyZ <[email protected]> * feat(jans-auth-server): agama consent script - set consent_flow into the session Signed-off-by: YuriyZ <[email protected]> * feat(jans-auth-server): agama consent script - added consetn gatherer service test Signed-off-by: YuriyZ <[email protected]> * doc(jans-auth-server): added documentation about consent script identification Signed-off-by: YuriyZ <[email protected]> --------- Signed-off-by: YuriyZ <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Currently it's invoked based on client configuration. However it shouldn't be problem to introduce new AS configuration property and invoke it based on acr if needed. For example
Test cases and code coverage
The text was updated successfully, but these errors were encountered: