Skip to content
New issue

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

Fix the ASP.NET Core Data Protection formatters to use the correct value type for the token lifetime claims #1975

Merged

Conversation

kevinchalet
Copy link
Member

Fixes #1974.

@@ -35,21 +35,10 @@ public ClaimsPrincipal ReadToken(BinaryReader reader)

.SetClaim(Claims.Private.HostProperties, GetJsonProperty(properties, Properties.HostProperties))

.SetClaim(Claims.Private.AccessTokenLifetime, GetProperty(properties, Properties.AccessTokenLifetime))
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Note: most of these mappings were useless as the validation stack only processes DP access tokens and these properties/claims are not present in access tokens.

@kevinchalet kevinchalet merged commit 253b1b5 into openiddict:dev Feb 9, 2024
6 checks passed
@kevinchalet kevinchalet deleted the formatter_claim_value_types branch February 9, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Data Protection causes claim value type to default to string
1 participant