-
Notifications
You must be signed in to change notification settings - Fork 344
WebView2
Bogdan Gavril edited this page Mar 17, 2021
·
15 revisions
A modern embedded browser based on Microsoft Edge, capable of performing Windows Hello, log in with FIDO keys etc. This browser replaces the old embedded webview, based on an outdated version of Internet Explorer.
- All Windows versions
- MSAL version 4.28.0 or higher
- WebView2 Runtime must be installed on the machine
WebView2 runtime is not available on Windows by default. Applications should install it or guide end users to install it. Installing it requires admin access.
As an alternative to the evergreen runtime, apps can bundle a fixed runtime.
var builder = pca.AcquireTokenInteractive(scopes)
.WithUseEmbeddedWebView(true);
// checks for the evergreen WebView2 runtime
if (!pca.IsEmbeddedWebViewAvailable())
{
builder = builder.WithEmbeddedWebViewOptions(
new EmbeddedWebViewOptions()
{
WebView2BrowserExecutableFolder = @"c:\my_app\webview2\fixed_version"
});
}
- On NET5-windows, there is no change
- On NET Classic and .NET Core 3.1, add a reference to Microsoft.Identity.Client.Desktop and call
.WithDesktopFeatures()
var pca = PublicClienntApplicationBuilder.Create("client_id")
.WithDesktopFeatures()
.Build()
Embedded WebView | Default WebView | |
---|---|---|
NET Fx | WebView2, fallback to Legacy | Embedded |
NET Core | WebView2 only | Embedded |
NET 5 | WebView2 only | Embedded |
- 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