Skip to content

Commit b12c774

Browse files
bugfix
1 parent f214be3 commit b12c774

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/active-directory/develop/msal-android-single-sign-on.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ ms.workload: identity
1111
ms.tgt_pltfrm: android
1212
ms.devlang: java
1313
ms.topic: how-to
14-
ms.date: 01/17/2023
14+
ms.date: 01/18/2023
1515
ms.author: henrymbugua
1616
---
1717

@@ -28,7 +28,7 @@ In this how-to, you'll learn how to configure the SDKs used by your application
2828
- Provision your app using the Azure portal. For more information about app provision, see the instructions for creating an app in [the Android tutorial](./tutorial-v2-android.md#create-a-project)
2929
- Integrate your application with the [MSAL for Android](https://github.com/AzureAD/microsoft-authentication-library-for-android)
3030

31-
## Methods for single sign-on
31+
## Methods for SSO
3232

3333
There are two ways for applications using MSAL for Android to achieve SSO:
3434

@@ -52,7 +52,7 @@ We recommend that you use one of Microsoft's authentication brokers to participa
5252

5353
On Android, the Microsoft Authentication Broker is a component that's included in the [Microsoft Authenticator](https://play.google.com/store/apps/details?id=com.azure.authenticator) and [Intune Company Portal](https://play.google.com/store/apps/details?id=com.microsoft.windowsintune.companyportal) apps.
5454

55-
The following diagram illustrates the relationship between your app, the Microsoft Authentication Library (MSAL), and Microsoft's authentication brokers.
55+
The following diagram illustrates the relationship between your app, the MSAL, and Microsoft's authentication brokers.
5656

5757
![Diagram showing how an application relates to MSAL, broker apps, and the Android account manager.](./media/brokered-auth/brokered-deployment-diagram.png)
5858

@@ -167,7 +167,7 @@ MSAL supports authorization using a `WebView`, or the system browser. The image
167167

168168
![MSAL login examples](./media/authorization-agents/sign-in-ui.jpg)
169169

170-
### Single sign-on implications
170+
### SSO implications
171171

172172
By default, applications integrated with MSAL use the system browser's Custom Tabs to authorize. Unlike WebViews, Custom Tabs share a cookie jar with the default system browser enabling fewer sign-ins with web or other native apps that have integrated with Custom Tabs.
173173

0 commit comments

Comments
 (0)