![]() ![]() To learn how to configure staged rollout, see the staged rollout interactive guide migration to cloud authentication using staged rollout in Azure AD). We recommend using staged rollout to test before cutting over domains. Refer to the staged rollout implementation plan to understand the supported and unsupported scenarios. String installPath = env = await CoreWebView2Environment.CreateAsync(installPath, userFolder, options) Īwait rollout is a great way to selectively test groups of users with cloud authentication capabilities like Azure AD Multi-Factor Authentication (MFA), Conditional Access, Identity Protection for leaked credentials, Identity Governance, and others, before cutting over your domains. var options = new CoreWebView2EnvironmentOptions(default, default, default, true) It is using Fixed Binaries, so passing a relative path. I've already tried setting the environment variable for AllowSingleSignOnUsingOSPrimaryAccount, but that didn't work. Find a parameter that enables it to login automatically.Launching and hiding a window that would persist the identity (very old-school).Prevent the deletion of the files providing identity.Is there a way to persist that login, so that after the window closes, subsequent windows reuse that login, along with maybe an expiration on the file(s) that have that information? If a webview2 app that has already stored the user identity is open, it seems to reuse that authentication. ![]() The one complaint we are getting from users is that the MS login gets 'forgotten' after the browser window closes, requiring that they login via a popup MS window on subsequent webview loads, and click on their identity. I am running into an issue, working win WebView2 in a WPF application. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |