Address Issue#735 - Initiating User Registration via OpenID Connect 1.0 - #907
Open
cybersreejith wants to merge 5 commits into
Open
Address Issue#735 - Initiating User Registration via OpenID Connect 1.0#907cybersreejith wants to merge 5 commits into
cybersreejith wants to merge 5 commits into
Conversation
azmeuk
self-requested a review
July 4, 2026 21:16
Author
|
@azmeuk - Would you please review the PR, provide review comments (if any), and stage it for merge? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a feature implementation for OpenID Connect Prompt Create support
fixes #735
It supports the create prompt value in authorization request handling, and it supports prompt_values_supported in discovery metadata.
Does this PR introduce a breaking change?
No.
Checklist
The commits follow the conventional commits
Yes
You ran the linters with prek
Yes
You wrote unit test to demonstrate the bug you are fixing, or to stress the feature you are bringing.
Yes
You reached 100% of code coverage on the code you edited, without abusive use of pragma: no cover
Yes
If this PR is about a new feature, or a behavior change, you have updated the documentation accordingly
Yes