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
Copy file name to clipboardExpand all lines: articles/active-directory/develop/msal-android-single-sign-on.md
+7-9Lines changed: 7 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ In this how-to, you'll learn how to configure the SDKs used by your application
27
27
28
28
This how-to assumes you know how to:
29
29
30
-
- Provision your app using the Azure portal. For more information, see the instructions for creating an app in [the Android tutorial](./tutorial-v2-android.md#create-a-project)
30
+
- Provision your app. For more information, see the instructions for creating an app in [the Android tutorial](./tutorial-v2-android.md#create-a-project)
31
31
- Integrate your application with the [MSAL for Android](https://github.com/AzureAD/microsoft-authentication-library-for-android)
32
32
33
33
## Methods for SSO
@@ -98,7 +98,7 @@ You must register a redirect URI that is compatible with the broker. The redirec
98
98
99
99
The format of the redirect URI is: `msauth://<yourpackagename>/<base64urlencodedsignature>`
100
100
101
-
You can use [keytool](https://manpages.debian.org/buster/openjdk-11-jre-headless/keytool.1.en.html) to generate a Base64-encoded signature hash using your app's signing keys, and then use the Azure portal to generate your redirect URI using that hash.
101
+
You can use [keytool](https://manpages.debian.org/buster/openjdk-11-jre-headless/keytool.1.en.html) to generate a Base64-encoded signature hash using your app's signing keys, and then generate your redirect URI using that hash.
Once you've generated a signature hash with _keytool_, use the Azure portal to generate the redirect URI:
116
116
117
-
1. Sign in to the <ahref="https://portal.azure.com/"target="_blank">Azure portal</a>.
118
-
1. If you have access to multiple tenants, use the **Directories + subscriptions** filter :::image type="icon" source="/azure/active-directory/develop/media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you registered your application.
119
-
1. Search for and select **Azure Active Directory**.
120
-
1. Under **Manage**, select **App registrations**.
121
-
1. Under **Manage**, select **App registrations**, then select your application.
122
-
1. Under **Manage**, select **Authentication** > **Add a platform** > **Android**.
117
+
1. Sign in to the [Microsoft Entra admin center](https://entra.microsoft.com) as at least an [Cloud Application Administrator](../roles/permissions-reference.md#cloud-application-administrator).
118
+
1. If access to multiple tenants is available, use the **Directories + subscriptions** filter :::image type="icon" source="media/common/portal-directory-subscription-filter.png" border="false"::: in the top menu to switch to the tenant in which you want to register the application.
119
+
1. Browse to **Identity** > **Applications** > **Application registrations**.
120
+
1. Select your application, and then select **Authentication** > **Add a platform** > **Android**.
123
121
1. In the **Configure your Android app** pane that opens, enter the **Signature hash** that you generated earlier and a **Package name**.
124
122
1. Select the **Configure** button.
125
123
126
-
The Azure portal generates the redirect URI for you and displays it in the **Android configuration** pane's **Redirect URI** field.
124
+
The redirect URI is generated for you and is displayed in the **Android configuration** pane's **Redirect URI** field.
127
125
128
126
For more information about signing your app, see [Sign your app](https://developer.android.com/studio/publish/app-signing) in the Android Studio User Guide.
0 commit comments