Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Extend the adal-node to msal-node migration docs with info on refresh tokens
See original GitHub issueLibrary
-
msal@1.x.xor@azure/msal@1.x.x -
@azure/msal-browser@2.x.x -
@azure/msal-node@1.x.x -
@azure/msal-react@1.x.x -
@azure/msal-angular@0.x.x -
@azure/msal-angular@1.x.x -
@azure/msal-angular@2.x.x -
@azure/msal-angularjs@1.x.x
Documentation location
- docs.microsoft.com
- MSAL.js Github Wiki
- README file
- Other (please fill in)
- Documentation does not exist
Description
One of the biggest points of confusion when migrating from adal-node to msal-node was for me the fact that msal-node (or MSAL in general) no longer exposes refresh tokens. Unless I totally missed it, the migration docs don’t mention this and I found the explanation in one of the issues in the repo. Since this is a big design change for folks coming from adal, it would be helpful to explain it upfront in the migration guidance including what’s the reasoning behind it and how it should be addressed.
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@waldekmastykarz Closing this. In case you have more concerns, please let us know and we can track it as needed.
@waldekmastykarz apologies for delay. I’ve updated the migration guide with how to migrate the still valid refresh tokens and a note on destroying the older adal-node token cache afterwards here. Hope this captures your concern, but let me know!