User is not redirected to redirect uri on mobile

[1hw7]

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)

[hectormmg]

@1hw7 is the postLogoutRedirectUri registered as a redirect URL and Logout URL in your app registration?

Here's the three requirements for successful redirection after logout:

1. Pass a postLogoutRedirectUri to logout
2. Register this url as a redirectUri on the app registration

Check out the MSAL Logout docs for more details.

[1hw7]

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]

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

[1hw7]

To update: user is not actually signed out and the user is sso'd back into the app. It seems the server session is not ended?

[sameerag]

Can we please get the msal and network logs @1hw7?

[ghost]

@1hw7 This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.

[sameerag]

Keeping this active. The team reached out to me offline and provided the needed information.

[tadeas22]

Same problem for me, please reopen

[gatsby-david]

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

[1hw7]

Hi @sameerag could we please reopen this issue(edit: i didn't realize my comment would reopen sorry!)? i do not think the issue has been resolved on our end

[bmahall]

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

[bmahall]

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

[ghost]

@1hw7 This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.

[1hw7]

Commenting to leave open, as the issue continues to persist

[ghost]

This issue requires attention from the MSAL.js team and has not seen activity in 5 days. @bmahall please follow up.

[ghost]

This issue requires attention from the MSAL.js team and has not seen activity in 5 days. @bmahall please follow up.

[ghost]

This issue requires attention from the MSAL.js team and has not seen activity in 5 days. @tnorling please follow up.

[sameerag]

@1hw7 Are we still stuck on this?

[ghost]

@1hw7 This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 5 days. If your issue has been resolved please let us know by closing the issue. If your issue has not been resolved please leave a comment to keep this open. It will be closed automatically in 7 days if it remains stale.

[1hw7]

@sameerag sorry i missed your comment! Thomas was able to help us look into it (thank you Thomas!). He gave us some insight on what might be going wrong on our end, we really appreciate the help!

[asimyaramis]

can u describe what is causing the error and how u solved? @1hw7