Change OidcEndpoint.Type for the dynamically registered client #43184
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.
Minor update to the code currently on
main
only.OidcEndpoint.Type
can be used to restrictOidcRequestFilter
, and soon,OidcResponseFilter
, to filtering specific OIDC endpoints only.As far as OIDC dynamic client registration is concerned, it can make calls to 2 endpoints:
OidcEndpoint.Type: CLIENT_REGISTRATION
).OidcEndpoint.Type: CLIENT_CONFIGURATION
endpoint type, but it does not feel quite right. PR proposes to change it toREGISTERED_CLIENT
, to align with theRegisteredClient
class name which manages the registered client