passport-azure-ad vs msal-node server side cache/storage

Core Library

MSAL Node (@azure/msal-node)

Core Library Version

1.8.0

Wrapper Library

Not Applicable

Wrapper Library Version

None

Description

From my understanding passport-azure-ad can be configured using cookie-session persisting authentication state in cookies and nothing is stored server side (relying on passport to validate the session etc). With msal-node, there is a default built in in-memory cache and extensions that allow you to persist authentication state to a data layer.

With passport-azure-ad now in maintenance, I was wondering/hoping if msal-node was planning on having a similar setup whereby a server side persistence layer is not needed?

For context, my use case is simply to protect a server endpoint from serving up static assets.

This may well be a silly question, or answered elsewhere but I can’t seem to find an answer.

MSAL Configuration

No response

Relevant Code Snippets

No response

Identity Provider

Azure AD / MSA

Source

External (Customer)

[tnorling]

@daniel-crouch We are working on a new token validation library that will replace passport-azure-ad. I don’t have an ETA to share at the moment but it is in active development and we can update this issue when the first version has been released

[msftbot[bot]]

@daniel-crouch This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.