The app clears its session objects, and the authentication library clears its token cache.The sign-out flow involves the following steps: If the Azure AD B2C session expires or becomes invalid, users are prompted to sign in again. If the Azure AD B2C SSO session is active, Azure AD B2C issues an access token without prompting users to sign in again. When the ID token is expired or the app session is invalidated, the app initiates a new authentication request and redirects users to Azure AD B2C. The app validates the ID token, reads the claims, and returns a secure page to users.
After users sign in successfully, Azure AD B2C returns an ID token to the app.Alternatively, they can sign in with a social account. Users sign up or sign in and reset the password.The app initiates an authentication request and redirects users to Azure AD B2C.Users go to the web app and select Sign-in.The sign in flow involves the following steps: Microsoft Identity Web is a set of ASP.NET Core libraries that simplify adding authentication and authorization support to web apps. This web app sample uses Microsoft Identity Web. You can use OIDC to securely sign users in to an application. OpenID Connect (OIDC) is an authentication protocol that's built on OAuth 2.0. For a web app that can call a REST API, see Secure a Web API that's built with ASP.NET Core by using Azure AD B2C. The sample ASP.NET web app that's referenced in this article can't be used to call a REST API, because it returns an ID token and not an access token.
0 kommentar(er)
