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.
Add support for the OIDC `max_age` parameter
See original GitHub issueCore Library
MSAL.js v2 (@azure/msal-browser)
Wrapper Library
Not Applicable
Description
The ability to force re-authentication by setting the OIDC max_age option (ref) was added to the MSAL Python library some time ago (1.15).
We have a need to FORCE re-authentication on a JS based SPA where a user is carrying out a privileged action (this is highly regulated environment) - could this feature be added to PublicClientApplication in parity with MSAL Python?
(BTW see this article to understand why login=prompt isn’t a good solution).
Source
External (Customer)
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (10 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
This is the first reference I could find that mentions max_age. It’s in the openid connect spec and Microsoft implemented it in Azure AD.
https://hajekj.net/2017/03/06/forcing-reauthentication-with-azure-ad/
You can use it to force re-authentication from the client side, but reading your explanation I guess you can implement continuous access evaluation to force re-authentication from the API side. I don’t have a good sample to do that, by the way.
@EmLauber CY22Q2 is drawing to a close - any update?