Bump jsonwebtoken to 9.0.0

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Upgrade fixes security vulnerabilities, but since it's a major version upgrade, some tests fail.

Feature / Enhancement Description

Adapt code for upgrade to 9.0.0.

Example Use Case

n/a

Alternatives / Workarounds

n/a

[mtrezza]

I assume this is related to the new auth adapter in Parse Server 6; could someone take a look? It's probably a tiny thing to fix. @Moumouls @dblythy

[Moumouls]

Hi @mtrezza it's not related to the new auth system, they just introduced some breaking changes.

here the migration guide for my self, i think it's an easy one: https://github.com/auth0/node-jsonwebtoken/wiki/Migration-Notes:-v8-to-v9

[mtrezza]

I meant that it's probably easy to fix for someone who worked on the recent auth PR, since it seems auth related. Thanks for posting the link, should make it easier for someone to pick this issue up.

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[parseplatformorg]

🎉 This change has been released in version 6.0.0-alpha.32

[parseplatformorg]

🎉 This change has been released in version 6.1.0-beta.1

[parseplatformorg]

🎉 This change has been released in version 6.1.0-alpha.1