![]() Grant your mobile app (App ID: 1) permissions to the web API scopes (App ID: 2). The app registration process generates an Application ID, which uniquely identifies your web API (for example, App ID: 2). The registration exposes the web API permissions (scopes). The web API registration enables your app to call a protected web API. The app registration process generates an Application ID, also known as the client ID, which uniquely identifies your mobile app (for example, App ID: 1). The redirect URI is the endpoint to which users are redirected by Azure AD B2C after they've authenticated with Azure AD B2C. ![]() ![]() During app registration, specify the redirect URI. The mobile application registration enables your app to sign in with Azure AD B2C. To enable your app to sign in with Azure AD B2C and call a web API, register two applications in the Azure AD B2C directory. It stores the tokens in an in-memory cache for later use.It exchanges the authorization code to an ID token, access token, and refresh token.After users sign in successfully, Azure AD B2C returns an authorization code to the app.Users sign up or sign in, reset the password, or sign in with a social account.The app opens the mobile device's system browser and starts an authentication request to Azure AD B2C.The sign-in flow involves the following steps: ![]() The MSAL is a Microsoft-provided library that simplifies adding authentication and authorization support to mobile apps. This mobile app sample uses the Microsoft Authentication Library (MSAL) with OIDC authorization code PKCE flow. 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. This article uses a sample Android application (Kotlin and Java) to illustrate how to add Azure Active Directory B2C (Azure AD B2C) authentication to your mobile apps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |