-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Labels
Needs: Attention 👋Awaiting response from the MSAL.js teamAwaiting response from the MSAL.js teamconfidential-clientIssues regarding ConfidentialClientApplicationsIssues regarding ConfidentialClientApplicationsfeature-unconfirmedmsal-nodeRelated to msal-node packageRelated to msal-node packagequestionCustomer is asking for a clarification, use case or information.Customer is asking for a clarification, use case or information.
Description
Core Library
MSAL Node (@azure/msal-node)
Wrapper Library
Not Applicable
Public or Confidential Client?
Confidential
Description
| "jsonwebtoken": "^9.0.0", |
auth0 themselves seem to recommend the jose library these days, and the jsonwebtoken package hasn't been updated in a few years now.
it may be worth switching to jose for a few reasons:
- it supports more algorithms
- it is around the same size (slightly smaller)
- it has no dependencies
- jsonwebtoken depends on long deprecated packages which are unmaintained and will never receive security updates (if ever needed)
thanks to the better support and more modern feature set, it is more likely to be adopted going forward than jsonwebtoken is. so we will also gain from npm de-dupe.
aylmercarson, beeequeue and v1rtl
Metadata
Metadata
Assignees
Labels
Needs: Attention 👋Awaiting response from the MSAL.js teamAwaiting response from the MSAL.js teamconfidential-clientIssues regarding ConfidentialClientApplicationsIssues regarding ConfidentialClientApplicationsfeature-unconfirmedmsal-nodeRelated to msal-node packageRelated to msal-node packagequestionCustomer is asking for a clarification, use case or information.Customer is asking for a clarification, use case or information.