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
title: Xamarin Android system browser considerations (MSAL.NET) | Azure
3
3
titleSuffix: Microsoft identity platform
4
-
description: Learn about specific considerations when using system browsers on Xamarin Android with Microsoft Authentication Library for .NET (MSAL.NET).
4
+
description: Learn about considerations for using system browsers on Xamarin Android with Microsoft Authentication Library for .NET (MSAL.NET).
5
5
services: active-directory
6
6
author: mmacy
7
7
manager: CelesteDG
@@ -14,18 +14,19 @@ ms.date: 10/30/2019
14
14
ms.author: marsma
15
15
ms.reviewer: saeeda
16
16
ms.custom: aaddev
17
-
#Customer intent: As an application developer, I want to learn about specific considerations when using Xamarin Android and MSAL.NET so I can decide if this platform meets my application development needs and requirements.
17
+
#Customer intent: As an application developer, I want to learn about considerations for using Xamarin Android and MSAL.NET so I can decide if this platform meets my application development needs.
18
+
ms.collection: M365-identity-device-management
18
19
---
19
20
20
-
# Xamarin Android system browser considerations with MSAL.NET
21
+
# Xamarin Android system browser considerations for using MSAL.NET
21
22
22
-
This article discusses specific considerations when using the system browser on Xamarin Android with the Microsoft Authentication Library for .NET (MSAL.NET).
23
+
This article discusses what you should consider when you use the system browser on Xamarin Android with Microsoft Authentication Library for .NET (MSAL.NET).
23
24
24
-
Starting with MSAL.NET 2.4.0-preview, MSAL.NET supports browsers other than Chrome and no longer requires Chrome be installed on the Android device for authentication.
25
+
Starting with MSAL.NET 2.4.0 Preview, MSAL.NET supports browsers other than Chrome. It no longer requires Chrome be installed on the Android device for authentication.
25
26
26
-
We recommend you use browsers that support custom tabs, such as these:
27
+
We recommend that you use browsers that support custom tabs. Here are some examples of these browsers:
27
28
28
-
| Browsers with custom tabs support | Package Name|
29
+
| Browsers that have custom tabs support | Package name|
29
30
|------| ------- |
30
31
|Chrome | com.android.chrome|
31
32
|Microsoft Edge | com.microsoft.emmx|
@@ -34,39 +35,39 @@ We recommend you use browsers that support custom tabs, such as these:
34
35
|Kiwi | com.kiwibrowser.browser|
35
36
|Brave | com.brave.browser|
36
37
37
-
In addition to browsers with custom tabs support, based on our testing, a few browsers that don't support custom tabs will also work for authentication: Opera, Opera Mini, InBrowser, and Maxthon. For more information, read [table for test results](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/Android-system-browser#devices-and-browsers-tested).
38
+
In addition to identifying browsers that offer custom tabs support, our testing indicates that a few browsers that don't support custom tabs also work for authentication. These browsers include Opera, Opera Mini, InBrowser, and Maxthon.
38
39
39
-
## Known issues
40
-
41
-
- If the user has no browser enabled on the device, MSAL.NET will throw an `AndroidActivityNotFound` Exception.
42
-
-**Mitigation**: Inform the user that they should enable a browser (preferably one with custom tabs support) on their device.
43
-
44
-
- If authentication fails (ex. authentication launches with DuckDuckGo), MSAL.NET will return an `AuthenticationCanceled MsalClientException`.
45
-
-**Root Problem**: A browser with custom tabs support was not enabled on the device. Authentication launched with an alternate browser, which wasn't able to complete authentication.
46
-
-**Mitigation**: Inform the user that they should install a browser (preferably one with custom tab support) on their device.
47
-
48
-
## Devices and browsers tested
49
-
The following table lists the devices and browsers that have been tested.
40
+
## Tested devices and browsers
41
+
The following table lists the devices and browsers that have been tested for authentication compatibility.
If the user has no browser enabled on the device, MSAL.NET will throw an `AndroidActivityNotFound` exception.
66
+
-**Mitigation**: Ask the user to enable a browser on their device. Recommend a browser that supports custom tabs.
68
67
69
-
* Supports custom tabs
68
+
If authentication fails (for example, if authentication launches with DuckDuckGo), MSAL.NET will return `AuthenticationCanceled MsalClientException`.
69
+
-**Root problem**: A browser that supports custom tabs wasn't enabled on the device. Authentication launched with a browser that couldn't complete authentication.
70
+
-**Mitigation**: Ask the user to enable a browser on their device. Recommend a browser that supports custom tabs.
70
71
71
72
## Next steps
72
-
For code snippets and additional information on using system browser with Xamarin Android, read this [guide](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/MSAL.NET-uses-web-browser#choosing-between-embedded-web-browser-or-system-browser-on-xamarinandroid).
73
+
For more information and code examples, see [Choosing between an embedded web browser and a system browser on Xamarin Android](https://github.com/AzureAD/microsoft-authentication-library-for-dotnet/wiki/MSAL.NET-uses-web-browser#choosing-between-embedded-web-browser-or-system-browser-on-xamarinandroid) and [Embedded versus system web UI](msal-net-web-browsers.md#embedded-vs-system-web-ui).
0 commit comments