We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Expected Behavior
RFC 9493 defines the "sub_id" claim for transmitting typed subject identifiers, rather than relying on the flat string of "sub".
Support for this at the Resource and Authroization servers would be very helpful, similar to the SAML ID support.
Current Behavior
Manually parsing and serialising the structures and string constants from/to the Map<String, Object> of claims.
Map<String, Object>
Context
Identifying users that may have multiple identifiers, federating across domains that may have identifier conflicts, etc.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Expected Behavior
RFC 9493 defines the "sub_id" claim for transmitting typed subject identifiers, rather than relying on the flat string of "sub".
Support for this at the Resource and Authroization servers would be very helpful, similar to the SAML ID support.
Current Behavior
Manually parsing and serialising the structures and string constants from/to the
Map<String, Object>
of claims.Context
Identifying users that may have multiple identifiers, federating across domains that may have identifier conflicts, etc.
The text was updated successfully, but these errors were encountered: