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.

Sign up for GitHub

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

Jump to bottom

JwtClaimsBuilder fails to enforce the correct type of directly supported claims #391

Closed
sberyozkin opened this issue Jan 20, 2021 · 1 comment · Fixed by #403
Closed

JwtClaimsBuilder fails to enforce the correct type of directly supported claims #391

sberyozkin opened this issue Jan 20, 2021 · 1 comment · Fixed by #403
Milestone
2.4.3

Comments

@sberyozkin
Copy link
Contributor

No description provided.

@sberyozkin
Copy link
Contributor Author

Quarkus user, instead of Jwt.subject("1") typed Jwt.claim(Claims.sub, 1), passing a number and it caused an error...

@sberyozkin sberyozkin added this to the 2.4.3 milestone Jan 20, 2021
@sberyozkin sberyozkin mentioned this issue Jan 20, 2021
Closed
@sberyozkin sberyozkin changed the title JwtClaimsBuilder fails to convert non-String objects to String for String-type claims JwtClaimsBuilder fails to enforce the correct type of the directly supported claims Jan 29, 2021
@sberyozkin sberyozkin changed the title JwtClaimsBuilder fails to enforce the correct type of the directly supported claims JwtClaimsBuilder fails to enforce the correct type of directly supported claims Jan 29, 2021
@sberyozkin sberyozkin mentioned this issue Jan 29, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
2.4.3
Development

Successfully merging a pull request may close this issue.

Enforce types of the directly supported claims when they are set as Objects
1 participant
@sberyozkin