New UI not generating tokens as previous one?

[fjakimowicz-da]

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?

[robecole1]

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.

[villecoder]

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.

[mcarbonera]

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.

[mcarbonera]

Another problem is that I can't edit decoded payload to get a new token.