Update OIDC clients to .NET 9 #1639
Merged
Conversation
This file contains 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
Now that PAR is enabled by default, these are redundant with MvcCode and MvcJarJwt
Use the new PushAuthorization event to send a JAR to the PAR endpoint.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Update our internal oidc clients to .NET 9, and give them some minor cleanups (disabling telemetry, fixing log levels, etc).
Notably, my work on PAR in the asp.net handler means all our OIDC test clients use PAR by default now. This means that we can discard the clients that specifically added PAR, as that is redundant
- MvcPar is gone, in favor of MvcCode, etc
- MvcJarPar is gone, in favor of MvcJarJwt, which is updated to use the new PAR event (the JAR it creates is pushed to the PAR endpoint, rather than sent to the authorize endpoint)
Also, I'm using the preview of Duende.AccessTokenManagement 3.1.