New UI not generating tokens as previous one? #764
Replies: 5 comments 2 replies
-
I'm having a similar problem where it's requiring to use a longer secret for UTF-8 when it was not a problem for the old UI. It won't be feasible to recreate every JWT I have due to needing a longer secret. |
Beta Was this translation helpful? Give feedback.
-
We use a base64 encoded key for signing our JWTs. Does "base64url" mean I need to submit a URL? My key isn't a URL. |
Beta Was this translation helpful? Give feedback.
-
This is exactly the problem I got right know. I can't find the "secret base64 encoded" checkbox on new UI. I'm using a base 64 decoder to use the tool. |
Beta Was this translation helpful? Give feedback.
-
It used to work, new UI/UX is broken. https://jwt.ms/ - all works fine here and it's clear design. |
Beta Was this translation helpful? Give feedback.
-
To clarify what's happening here: "base64url" is the name of a variant of base64 encoding designed to be safe for use in URLs and filenames: normal base64 uses So for instance, the binary data which encodes to There appear to be two problems here:
So to be clear having validation in the new UI is a good thing, it just needs to be tweaked:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When i generate a token from the old ui using the option secret base64 encoded, all goes fine.

However if i do the same with the new one, it generates a different token, which of course fails authentication.
If i encode the token in base64 beforehand and select base64URL it also fails.
So, how can i achieve the same results that with the prev version?
Beta Was this translation helpful? Give feedback.
All reactions