How to get ID token claims for existing sessions #1905
Labels
msal-browser
Related to msal-browser package
question
Customer is asking for a clarification, use case or information.
Library
msal@1.x.x
or@azure/msal@1.x.x
@azure/msal-browser@2.0.0-beta.4
@azure/msal-angular@0.x.x
@azure/msal-angular@1.x.x
@azure/msal-angularjs@1.x.x
Description
I'm updating my POC app from beta.2 to beta.4. It looks like the account object that is persisted for a session is much more limited than before and doesn't include the id token claims. My app needs access to the id token claims so this change impacts my app initialization - if I'm getting a fresh session from the server I'll get the id token claims and proceed as usual, but, if I'm initializing with an existing session I don't have access to this data now so my question is - what is the recommended way to get id token claims for an existing session?
Currently I'm working around this by getting the id token data from a subsequent access token request but I'd prefer a solution that's not coupled to other operations. From a performance perspective I'd actually prefer if the claims could be returned from a cache so that we don't incur a new delay to fetch id tokens when we're initializing an existing session.
The text was updated successfully, but these errors were encountered: