-
Notifications
You must be signed in to change notification settings - Fork 344
Android system browser
Starting with MSAL.NET 2.4.0-preview (not yet released), MSAL.NET supports browsers other than Chrome and no longer requires Chrome be installed on the Android device for authentication.
It is recommended to use browsers which support custom tabs, such as the following browsers:
Browsers with custom tabs support | Package Name |
---|---|
Chrome | com.android.chrome |
Microsoft Edge | com.microsoft.emmx |
Firefox | org.mozilla.firefox |
Ecosia | com.ecosia.android |
Kiwi | com.kiwibrowser.browser |
Brave | com.brave.browser |
In addition to browsers with custom tab support, based on our testing, a few browsers that do not support custom tabs will also work for authentication, such as Opera, Opera Mini, InBrowser, and Maxthon. See table for test results.
-
If the user has no browser enabled on the device, MSAL.NET will throw an
ActivityNotFoundException
with a link to this page. You will want to suggest the user enable a browser (preferably one with custom tab support) on their device. -
If authentication fails (ex. authentication launches with DuckDuckGo and we know this will fail), MSAL.NET will return an
AuthenticationCanceled MsalClientException
, with a link to this page. You will want to suggest the user install a browser (preferably one with custom tab support) on their device.
Browser* | Result | |
---|---|---|
Huawei/One+ | Edge* | Pass |
Huawei/One+ | Firefox* | Pass |
Huawei/One+ | Brave* | Pass |
One+ | Ecosia* | Pass |
One+ | Kiwi* | Pass |
Huawei/One+ | Opera | Pass |
Huawei | OperaMini | Pass |
Huawei/One+ | InBrowser | Pass |
One+ | Maxthon | Pass |
Huawei/One+ | DuckDuckGo | User cancelled auth |
Huawei/One+ | UC Browser | User cancelled auth |
One+ | Dolphin | User cancelled auth |
One+ | CM browser | User cancelled auth |
Hauwei/One+ | none installed | AndroidActivityNotFound ex |
Supports Custom Tabs*
See this guide with code snippets and additional information on using system browser with Xamarin Android.
- Home
- Why use MSAL.NET
- Is MSAL.NET right for me
- Scenarios
- Register your app with AAD
- Client applications
- Acquiring tokens
- MSAL samples
- Known Issues
- AcquireTokenInteractive
- WAM - the Windows broker
- .NET Core
- Maui Docs
- Custom Browser
- Applying an AAD B2C policy
- Integrated Windows Authentication for domain or AAD joined machines
- Username / Password
- Device Code Flow for devices without a Web browser
- ADFS support
- Acquiring a token for the app
- Acquiring a token on behalf of a user in Web APIs
- Acquiring a token by authorization code in Web Apps
- High Availability
- Token cache serialization
- Logging
- Exceptions in MSAL
- Provide your own Httpclient and proxy
- Extensibility Points
- Clearing the cache
- Client Credentials Multi-Tenant guidance
- Performance perspectives
- Differences between ADAL.NET and MSAL.NET Apps
- PowerShell support
- Testing apps that use MSAL
- Experimental Features
- Proof of Possession (PoP) tokens
- Using in Azure functions
- Extract info from WWW-Authenticate headers
- SPA Authorization Code