Outdated and incorrect documentation on distributed caching in `@azure/msal-node`
See original GitHub issueCore Library
MSAL Node (@azure/msal-node)
Wrapper Library
Not Applicable (edit: removed angular, not applicable).
Documentation Location
Description
The example provided here doesn’t seem to be correct anymore.
This line in the cachePlugin.js
file refers to the method getKVStore()
that no longer exists on the object. What would be the appropriate alternative for @azure/msal-node
v1.7.0?
I’ve been looking for good documentation on how to implement an express application (or any web application really) that supports multi-user authentication while protecting each users cached credentials correctly. Many different MS specific sites such as this and this eventually lead back the above example. And since the example no longer works it is hard to know the correct way to implement this.
Authentication is already pretty hard to get right so I feel it is critical to have good documentation on how to distribute cached credentials correctly using msal
. Especially when the library is recommended by Microsoft.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top GitHub Comments
@jon-a-nygaard apologies for the confusion. This sample was demoing an initial approach to distributed caching, but since then msal-node was updated and a more mature pattern has been implemented here -can you please refer to that sample instead? I’ll keep this open to update the ExpressTestApp sample and the distributed caching doc to clarify things.
Thanks for the quick reply and help @derisen, I will look to the
RedisTestApp
sample. Glad to see that you’re updating the docs as well 🙂