You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I am wondering if it is possible from a custom widget on the portal to get the token from the logged in user using the @azure/msal-browser package? Using the @azure/api-management-custom-widgets-tools package and the askForSecrets() I can get the SAS token from the login but not the MSAL OAuth token.
I need the OAuth token from the login. If I use the @azure/msal-browser package and the function aquireTokenXXX methods then the user is forced to log in a second time when my widget is loaded on the portal. It seems the msal session storage is separate for the portal an my widget on the portal due to sandboxing?
Is there any way of getting the portal sign-in OAuth Token from my widget just as I can get the SAS token by calling askForSecrets() ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I am wondering if it is possible from a custom widget on the portal to get the token from the logged in user using the @azure/msal-browser package? Using the @azure/api-management-custom-widgets-tools package and the askForSecrets() I can get the SAS token from the login but not the MSAL OAuth token.
I need the OAuth token from the login. If I use the @azure/msal-browser package and the function aquireTokenXXX methods then the user is forced to log in a second time when my widget is loaded on the portal. It seems the msal session storage is separate for the portal an my widget on the portal due to sandboxing?
Is there any way of getting the portal sign-in OAuth Token from my widget just as I can get the SAS token by calling askForSecrets() ?
Beta Was this translation helpful? Give feedback.
All reactions