You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this article, you learn how to provide sign-up and sign-in to customers with [Mobile ID](https://www.mobileid.ch)accounts in your applications using Azure Active Directory B2C (Azure AD B2C). The Mobile ID solution protects access to your company data and applications with a comprehensive end-to- end solution for a strong multi-factor authentication (MFA). You add the Mobile ID to your user flows or custom policy using OpenID Connect protocol.
22
+
In this article, you learn how to provide sign-up and sign-in to customers with [Mobile ID](https://www.mobileid.ch) in your applications using Azure Active Directory B2C (Azure AD B2C). The Mobile ID solution protects access to your company data and applications with a comprehensive end-to- end solution for a strong multi-factor authentication (MFA). You add the Mobile ID to your user flows or custom policy using OpenID Connect protocol.
To enable sign-in for users with a Mobile ID account in Azure AD B2C, you need to create an application. To create Mobile ID application, follow these steps:
30
+
To enable sign-in for users with Mobile ID in Azure AD B2C, you need to create an application. To create Mobile ID application, follow these steps:
31
31
32
32
1. Contact [Mobile ID support](https://www.mobileid.ch/en/contact).
33
33
1. Provide the Mobile ID the information about your Azure AD B2C tenant:
@@ -65,7 +65,7 @@ To enable sign-in for users with a Mobile ID account in Azure AD B2C, you need t
65
65
1. For **Client secret**, enter the Mobile ID client secret.
66
66
1. For the **Scope**, enter the `openid, profile, phone, mid_profile`.
67
67
1. Leave the default values for **Response type** (`code`), and **Response mode** (`form_post`).
68
-
1. (Optional) For the **Domain hint**, enter `mobileid.com`. For more information, see [Set up direct sign-in using Azure Active Directory B2C](direct-signin.md#redirect-sign-in-to-a-social-provider).
68
+
1. (Optional) For the **Domain hint**, enter `mobileid.ch`. For more information, see [Set up direct sign-in using Azure Active Directory B2C](direct-signin.md#redirect-sign-in-to-a-social-provider).
69
69
1. Under **Identity provider claims mapping**, select the following claims:
70
70
71
71
- **User ID**: *sub*
@@ -79,13 +79,13 @@ To enable sign-in for users with a Mobile ID account in Azure AD B2C, you need t
79
79
At this point, the Mobile ID identity provider has been set up, but it's not yet available in any of the sign-in pages. To add the Mobile ID identity provider to a user flow:
80
80
81
81
1. In your Azure AD B2C tenant, select **User flows**.
82
-
1. Click the user flow that you want to add the Mobile ID identity provider.
82
+
1. Select the user flow that you want to add the Mobile ID identity provider.
83
83
1. Under the **Social identity providers**, select **Mobile ID**.
84
84
1. Select **Save**.
85
85
1. To test your policy, select **Run user flow**.
86
86
1. For **Application**, select the web application named *testapp1* that you previously registered. The **Reply URL** should show `https://jwt.ms`.
87
87
1. Select the **Run user flow** button.
88
-
1. From the sign-up or sign-in page, select **Mobile ID** to sign in with Mobile ID account.
88
+
1. From the sign-up or sign-in page, select **Mobile ID** to sign in with Mobile ID.
89
89
90
90
If the sign-in process is successful, your browser is redirected to `https://jwt.ms`, which displays the contents of the token returned by Azure AD B2C.
91
91
@@ -106,16 +106,16 @@ You need to store the client secret that you received from Mobile ID in your Azu
106
106
7. Enter a **Name** for the policy key. For example, `Mobile IDSecret`. The prefix `B2C_1A_` is added automatically to the name of your key.
107
107
8. In **Secret**, enter your Mobile ID client secret.
108
108
9. For **Key usage**, select `Signature`.
109
-
10. Click **Create**.
109
+
10. Select **Create**.
110
110
111
111
## Configure Mobile ID as an identity provider
112
112
113
-
To enable users to sign in using a Mobile ID account, you need to define the account as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify that a specific user has authenticated.
113
+
To enable users to sign in using a Mobile ID, you need to define the Mobile ID as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify that a specific user has authenticated.
114
114
115
-
You can define a Mobile ID account as a claims provider by adding it to the **ClaimsProviders** element in the extension file of your policy.
115
+
You can define a Mobile ID as a claims provider by adding it to the **ClaimsProviders** element in the extension file of your policy.
116
116
117
117
1. Open the *TrustFrameworkExtensions.xml*.
118
-
2. Find the **ClaimsProviders** element. If it does not exist, add it under the root element.
118
+
2. Find the **ClaimsProviders** element. If it doesn't exist, add it under the root element.
119
119
3. Add a new **ClaimsProvider** as follows:
120
120
121
121
```xml
@@ -189,20 +189,13 @@ You can define a Mobile ID account as a claims provider by adding it to the **Cl
189
189
1. Select your relying party policy, for example `B2C_1A_signup_signin`.
190
190
1. For **Application**, select a web application that you [previously registered](tutorial-register-applications.md). The **Reply URL** should show `https://jwt.ms`.
191
191
1. Select the **Run now** button.
192
-
1. From the sign-up or sign-in page, select **Mobile ID** to sign in with Mobile ID account.
192
+
1. From the sign-up or sign-in page, select **Mobile ID** to sign in with Mobile ID.
193
193
194
194
If the sign-in process is successful, your browser is redirected to `https://jwt.ms`, which displays the contents of the token returned by Azure AD B2C.
195
195
196
196
197
197
::: zone-end
198
198
199
-
## Move to production
200
-
201
-
Mobile ID IdP provides Pre-production and Production environments. The configuration described in this article uses the pre-production environment. To use the production environment, follow these steps:
202
-
203
-
1. Contact Mobile ID support for a production environment.
204
-
1. Update your user flow or custom policy with the URI of the well-known configuration endpoint.
205
-
206
199
## Next steps
207
200
208
201
Learn how to [pass Mobile ID token to your application](idp-pass-through-user-flow.md).
0 commit comments