microsoft-authentication-library-for-js: User is not redirected to redirect uri on mobile

Core Library

MSAL.js v2 (@azure/msal-browser)

Core Library Version

2.24.0

Wrapper Library

MSAL React (@azure/msal-react)

Wrapper Library Version

1.4.0

Public or Confidential Client?

Public

Description

On mobile (safari and edge) when a user logs out, it hangs on the “you have logged out page” and the redirect uri does not seem to be triggered (user is never redirected to redirect uri)

Error Message

No response

Msal Logs

No response

MSAL Configuration

auth: {
        clientId: config.auth.clientId,
        authority: 'https://login.microsoftonline.com/consumers',
        redirectUri: `${config.auth.redirectUrl || config.sasUrl}/home`,
        navigateToLoginRequestUrl: false,
        postLogoutRedirectUri: `${config.auth.redirectUrl || config.sasUrl}`,
    },
    cache: {
        cacheLocation: BrowserCacheLocation.SessionStorage,
    }

Relevant Code Snippets

used button click to trigger signout, used instance.logoutredirect on button click

Reproduction Steps

  1. Open safari on mobile
  2. Click sign out button
  3. User is signed out, but never redirected back to redirect uri

Expected Behavior

User should be redirected to redirect uri

Identity Provider

Azure AD / MSA

Browsers Affected (Select all that apply)

Edge, Safari

Regression

No response

Source

Internal (Microsoft)

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 1
  • Comments: 26 (8 by maintainers)

Most upvoted comments

Commenting to leave open, as the issue continues to persist

Thanks for your help Hector! Yes, it is and this works for us in desktop. The issue only arises on a mobile device edit: actually, it’s possible we didn’t configure this correctly! sorry, double checking now. Thank you!

@1hw7 Please share logs on the email mentioned on my profile if possible , looking forward to chat on Monday when you are next available.

@1hw7 I am in touch with @sameerag and will get back on this on priority. Thanks

@bmahal Can we prioritize to root cause this?

The issue is auto closed. This will be kept open.

For me, the bug is happening only in Chrome on mobile. FF is ok.

Same problem for me, please reopen

We confirmed that our implementation follows the docs you linked Hector (thank you!) so we are awaiting further context on what the error is and how we can solve this problem