Single Sign Out (Single Logout) with Azure AD B2C

This video explains Sign Out and Single Sign Out concepts with the Azure AD B2C.
Helpful links:
Sign out with Azure AD B2C:
learn.microsoft.com/en-us/azu...
Single Sign Out with Azure AD B2C:
learn.microsoft.com/en-us/azu...

[@johngrant7097]

Great Video are you able to link to your GIT Repo for source code?

[@sushanth587]

What is _userSessionStateService, where did you reference the variable and what does the UpdateSessionState do, can you share the code snippet please

[@nryttv3]

Great video! How can this be handled in scenario where end user doesnt click logout but just closes the browser?

[@rickfiji4486]

Great video! Would you be able to upload your source code?

[@user-mp4iw5on6g]

I am having a SPA apps and doing the same steps as described. In front channel logout URL i am loading msal.js and trying to logout of b2c. however localStorage or sessionStorage is not shared when loaded via frontchannel logout url. If i directly launch front channel logout url then B2C logout happens but not when loaded in a . Do you know what could be wrong? is front channel logout not supported for SPA's?

[@TechMindFactory]

It looks like this is the problem with cookie access. Do you have "SameSite" set to none for your cookie?

[@linzhang5497]

Great Video! But for the Session Behavior on User Flow, The Require ID Token in logout request should be "Yes" , right? Also, does User Flow support Single Log out?

[@TechMindFactory]

Thank you! Require ID Token in logout should be yes to increase security - this can be set for both, user flows and custom policies. When it comes to Single Logout - as per my knowledge it is supported only with custom policies because you have to adjust technical profiles. Here is the session provider used to enable SLO: learn.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-reference-sso#oauthssosessionprovider

[@linzhang5497]

@@TechMindFactory Thank you so much for your reply. It is the best video about single log out online. I followed the steps you have, but the front channel URL is not getting called. I feel I am missing something.

[@TechMindFactory]

@@linzhang5497 Thank you for kind words. When it comes to your issue - I assume you used custom policies. Did you add technical profile called "SM-jwt-issuer" like presented here: learn.microsoft.com/en-us/azure/active-directory-b2c/custom-policy-reference-sso#oauthssosessionprovider and then used it as validation technical profile in the profile called "JwtIssuer" like this: Please check the link I added above - you have to use "SM-jwt-issuer" with type "OAuthSSOSessionProvider" . Here is the part that is the most important from the docs: This type of session provider allows Azure AD B2C to track all OAuth2 or OpenId Connect applications the user logged into. During the sign-out of one application, Azure AD B2C will attempt to call the logout endpoints of all other known logged in applications.

[@AshishPatel-dw1bi]

Hi, I will followed your steps but still not get to get single sign out for another application. so can you please give share check points to confirm? If needed, will you be available on demand hourly bases? Thank you

[@mayrinvarkey9134]

If we are using Saml 2 instead of OIDC how can I redirect to to a url. Do I still rely on post_logout_redirect_uri?

[@TechMindFactory]

For SAML service providers, configure the application with the SingleLogoutService location in its SAML metadata document. You can also configure the app registration logoutUrl. Please read here, there are details for both OIDC and SAML: learn.microsoft.com/en-us/azure/active-directory-b2c/session-behavior?pivots=b2c-custom-policy#configure-your-application

[@Fernando.Oliveira.]

👏🏻

[@nuskyfaizal9187]

Could you share the Source Code please

[@niteshsetin]

Hi, i am stuck in a problem , if user open blazor wasm app multiple tabs and log out from one of tabs then it is still logged in in another tabs. Please let me know how can i solve this or any video you can share

[@user-fz2gk9nh8h]

have to done this please explain me getting the same

[@niteshsetin]

@@user-fz2gk9nh8h I have achieved this using blazor wasm and local storage