Closed Bhargav-Narayan closed 4 years ago
This issue has not seen activity in 14 days. It may be closed if it remains stale.
Can someone provide status of this issue?
This issue has not seen activity in 14 days. It may be closed if it remains stale.
From what i can tell, this is not an MSAL issue. It is incorrect configuration in the policy for SSO. When SSO fails, MSAL throws x-frame-options: deny
error. I'll need to review the sample.
This issue has not seen activity in 14 days. It may be closed if it remains stale.
Closing due to inactivity. Please let us know if this is still an issue so we can reopen it.
Library
msal@1.2.0
Framework
React 16.8.4
Description
We have configured our AAD B2C tenant for impersonation flow by following github link ‘https://github.com/azure-ad-b2c/samples/tree/master/policies/impersonation’. We also tested this configuration and successfully generated the access token with impersonated user Sign In Name.
But when we configure our REACT JS application with MSAL library for impersonation flow, it is not working as expected.
We have tried with different access token method, below are the result -
Using aquireTokenSilent to get accesstoken. Both in Chrome and IE, it throws X-Frame-Options deny error after login and entering impersonated email id.
Using aquireTokenRedirect to get accesstoken Both in Chrome and IE, after successful login, it would repeatedly show the Impersonated user id Page and this would never go to our application Home Page
Using aquireTokenPopup to get accesstoken
Chrome
IE
Security
Is this issue security related? No
Regression
Did this behavior work before? Never tried
Configuration
Reproduction steps
Expected behavior
Once the user login to our app, he/she should be prompted to enter the login ID of the user that he/she wants to impersonate. Once submitted, user should be able to access our app with the entered impersonated user account
Browsers
IE 11, Chrome, Firefox