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

Token typ must be explicit to avoid token confusion #555

Open
peppelinux opened this issue Feb 12, 2025 · 0 comments
Open

Token typ must be explicit to avoid token confusion #555

peppelinux opened this issue Feb 12, 2025 · 0 comments
Assignees
@giadas @Sh-Amir
Labels
national-guidelines needs-discussion security standardization Topics related to the standardization process in IETF/OIDF

Comments

@peppelinux
Copy link
Member

https://www.rfc-editor.org/rfc/rfc8725.html#section-3.11

please inform PDND team

Originally posted by @peppelinux in #541 (comment)
@peppelinux peppelinux added security standardization Topics related to the standardization process in IETF/OIDF needs-discussion national-guidelines labels Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@giadas giadas

@Sh-Amir Sh-Amir

Labels
national-guidelines needs-discussion security standardization Topics related to the standardization process in IETF/OIDF
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@peppelinux @giadas @Sh-Amir