New JWT public key format issue


The new JWT public key from, the second public key, seems to be not correctly encoded. ‘\n’ gets escaped into ‘\n’, makes the public key string invalid, or have to be unescaped before use.

Is this a permanent change?

Hi Trello,

Is this going to be resolved?

Hi all! Thanks for the surfacing the issue. This was not an intentional change and we’re in the process of fixing it. To be clear, the private key has not been rotated yet, so verification of t.jwt() will still work as before using the original public key. Thanks for your patience.


UPDATE: The issue has been fixed. Thanks for everyone’s patience!

Hi Jireh,

Do you have any ETA for when this fixed is released? We’re also experiencing this issue when users install our Power Up.