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

Debugger support for unsecured JWTs #577

Open
JustinIven opened this issue Jan 25, 2022 · 2 comments
Open

Debugger support for unsecured JWTs #577

JustinIven opened this issue Jan 25, 2022 · 2 comments
Assignees
@DanOnCall

Comments

@JustinIven
Copy link

Support for "none" in the JOSE header according to RFC 7519 section 6
@panva panva mentioned this issue Mar 18, 2022
Closed
@stale
Copy link

stale bot commented Apr 25, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇‍♂️

@stale stale bot added the closed:stale label Apr 25, 2022
@stale stale bot closed this as completed May 4, 2022
@DanOnCall DanOnCall reopened this Jun 18, 2024
@stale stale bot removed the closed:stale label Jun 18, 2024
@DanOnCall
Copy link
Contributor

Justin, I am one of the newly appointed maintainers for jwt.io and I am working on a new version. I think this is a solid feature request and I am adding it to the roadmap for the next version 💪 cc @byron-okta

@DanOnCall DanOnCall self-assigned this Jun 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DanOnCall DanOnCall

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

support unsecured jwt
2 participants
@DanOnCall @JustinIven