Replies: 1 comment
-
I am facing this issue as well, where the public key field is no longer populated from the URL fragment. The "Share JWT" button as mentioned in this StackOverflow answer seems to be missing altogether. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
In the old version, I could generate a JWT and share both the JWT and the public key to verify it in a single link:
https://jwt.io/#debugger-io?token=eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.tyh-VfuzIxCyGYDlkBA7DfyjrqmSHu6pQ2hoZuFqUSLPNY2N0mpHb3nk5K17HWP_3cYHBw7AhHale5wky6-sVA&publicKey=-----BEGIN%20PUBLIC%20KEY-----%0AMFkwEwYHKoZIzj0CAQYIKoZIzj0DAQcDQgAEEVs%2Fo5%2BuQbTjL3chynL4wXgUg2R9%0Aq9UU8I5mEovUf86QZ7kOBIjJwqnzD1omageEHWwHdBO6B%2BdFabmdT9POxg%3D%3D%0A-----END%20PUBLIC%20KEY-----
When opening this link, the old version picked up the public key from the URI fragment, and automatically filled it in.
This was a convenient way to quickly show to users (especially the ones who aren't familiar with JWT format) how to understand the JWT content, and to "prove" that the JWT signature is valid against the provided public key.
These links are now broken after switching to the new UI: the public key provided in the URI seems to be simply ignored.
Is there any way to bring back that feature ? Ideally in a backward-compatible way, so that the links already shared keep working on the new version.
Beta Was this translation helpful? Give feedback.
All reactions