Emit RFC 9207 iss authorization-response parameter#534
Merged
Conversation
Upstream's COMPLIANT_BCP_RFC9700_AUTHZ_RESPONSE_ISS gate cannot derive our per-host "https://<host>/o2" issuers, so it is pinned False and mailauth.oauth2_backends.MNOAuthLibCore appends the correct `iss` value to successful authorization redirects instead. Both discovery documents (OIDC and RFC 8414) now advertise authorization_response_iss_parameter_supported via a shared mixin on wrapped views swapped into all three discovery mounts. Error redirects and RFC 7592/CIMD are out of scope for this change. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AgWqnQ8ExYjdZofXbvJZEz
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.
Upstream's COMPLIANT_BCP_RFC9700_AUTHZ_RESPONSE_ISS gate cannot derive our per-host "https:///o2" issuers, so it is pinned False and mailauth.oauth2_backends.MNOAuthLibCore appends the correct
issvalue to successful authorization redirects instead. Both discovery documents (OIDC and RFC 8414) now advertiseauthorization_response_iss_parameter_supported via a shared mixin on wrapped views swapped into all three discovery mounts. Error redirects and RFC 7592/CIMD are out of scope for this change.
Claude-Session: https://claude.ai/code/session_01AgWqnQ8ExYjdZofXbvJZEz