![]() ![]() The user takes action depending on the user flow. When your web application needs to authenticate the user and run a user flow, it can direct the user to the /authorize endpoint. It introduces the user flow parameter, which enables you to use OpenID Connect to add user experiences to your application, such as sign up, sign in, and profile management. For more information about tokens, see the Overview of tokens in Azure Active Directory B2CĪzure AD B2C extends the standard OpenID Connect protocol to do more than simple authentication and authorization. OpenID Connect is recommended if you're building a web application that's hosted on a server and accessed through a browser. You can use access tokens to access resources that are secured by an authorization server. It introduces the concept of an ID token, which allows the client to verify the identity of the user and obtain basic profile information about the user.īecause it extends OAuth 2.0, it also enables applications to securely acquire access tokens. This authentication protocol allows you to perform single sign-on. OpenID Connect extends the OAuth 2.0 authorization protocol for use as an authentication protocol. For more information, see Overview of the Microsoft Authentication Library (MSAL), and Microsoft Identity Web authentication library. We recommend exploring those options, rather than implementing your own code. Most of the open-source authentication libraries acquire and validate the JWT tokens for your application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |