Pixelatex

Can we atleast add this to the docs to clarify this? Spent quite searching for a weak bug that turns out to be caused by this.

So I was also getting this issue and mine seemed to be a potential memory leak. I optimised my code so less stuff is stored in memory and the errors...

@tlvince you rolled your own? A validator function or a replacement for 'validate' altogether? I have the exact same issue :/

This is still an issue it seems.. any fixes?

+1 also running into this now.. any updates yet?

aha mine is: ``` { "alg": "HS512" } ```

I used `https://mkjwk.org/` to generate a token as RS256 but now they keep coming back as signature invalid in jwt.io. Example jwt: ``` eyJraWQiOiJpcnE0SHduaFlFNzBBZ3BJZ3FvNDVHUVFZMkk0TjRBNUkxVVpkdHE2Q0p3IiwiYWxnIjoiUlMyNTYifQ.eyJ2ZXIiOjEsImp0aSI6IkFULnhQejBrdjM2OTNhZUpHSUZfWUtrTVZCdmE5ZjhjR0hTV0RWN1BWbXlIQWciLCJpc3MiOiJodHRwczovL2JvdGhycy5va3RhLmNvbSIsImF1ZCI6Imh0dHBzOi8vYm90aHJzLm9rdGEuY29tIiwic3ViIjoiZXdhcmRAYm90aHJzLmNvbSIsImlhdCI6MTYyMDc0NjEyMiwiZXhwIjoxNjIwNzQ5NzIyLCJjaWQiOiIwb2FvMW8yNzJ3WDB5T0YyMjVkNiIsInVpZCI6IjAwdW54MjM3dXVIZnlOQVVzNWQ2Iiwic2NwIjpbIm9wZW5pZCIsInByb2ZpbGUiLCJlbWFpbCIsImdyb3VwcyJdfQ.DhhTXtk9V3aMwg5gXng6oLztVEk6bLR6lAT8uzgeEB50_9fvtdntuua64mFhZzfqRBDH0sb4WAxUIHu-TeulSxn1LfcwTz43FdnHHm_FEAfNMCjXhp3Nnp2P9zToMruGG0gVNvMjeR-j1EU4XU6VW8lRDoTCeb8z1NJlBkqHFaOyjOjngal1caINfLyzf9VzUQnnmadHgo-hfBZQmU281SFFSSrMoj9mmrlAM_az7d2NLxabqRHNjvFuPQ1SeskUVhFm0SDMUJlrmjeVWbjX7FdIdUZeuPj2INfXhHKoPXR8zuZziyh93KNso1lBdRwK-p5SSXBdtmCTGUVmGT3xWg ```

@denysoblohin-okta straight from the okta documentation: ``` algorithm(dropdown): Okta Workflows supports the following types of JWT encryption: HS256 (default) HS384 HS512 RS256 RS384 RS512 ES256 ES384 ES512 PS265 PS384 PS512...

Especially because HS256 is the default setting here :/

I worked around this in a creative way... ``` export function Password({ onChange, value, placeholder }: Props) { const [hideValue, setHideValue] = useState(true) const [pwd, setPwd] = useState(value || '')...