WebAuthenticationBroker from ViewModel?

[weitzhandler]

Hi,

I wonder if there is any documentation on how to handle authentication identity, token, claims, and user, from when the UI logic is decoupled into a ViewModel etc. layer that's UI-agnostic.

Related: microsoft/WindowsAppSDK#31

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 3c758cb2-ad03-f28e-6947-21337462753a
• Version Independent ID: 3e818dc7-e032-c92b-80ba-0c0773391fec
• Content: WebAuthenticationBroker Class (Windows.Security.Authentication.Web) - Windows UWP applications
• Content Source: winrt-api-build/xml/Windows.Security.Authentication.Web/WebAuthenticationBroker.xml
• Product: uwp
• Technology: winrt-reference
• GitHub Login: @lastnameholiu
• Microsoft Alias: alholiu

[bgavrilMS]

@weitzhandler - I'm providing a few ideas based on my experience as the MSAL.NET developer. MSAL.NET integrates with WAB.

WAB is deprecated and as far as I know there is no new feature work happening there. I have not investigated if there are win32 projections of the WAB API.

I would suggest instead you look at WAM, which provides much better support especially around device authentication, integration with Windows Hello etc. There are win32 projections of the WAM API. From my experience with integrating with WAM (currently in progress), the difference between UWP and Win32 is:

• on Win32, you are required to parent the Authentication controls to the a window handle
• on UWP, this is not required, because you can always get the current view
• on both, some of Authentication popups require you to be on an UI thread

[weitzhandler]

Thanks @bgavrilMS for your kind and detailed reply,

MSAL.NET

MSAL doesn't cover custom identity management or legacy authentication with username & password against a private authentication provider (AzureAD/microsoft-authentication-library-for-dotnet#1538).

I would suggest instead you look at WAM

Sorry I mixed between WAB and WAM.

Anyway, as I commented here, I wish there was a lower level agnostic abstraction of client-side authentication flow and token management that can be managed in the ViewModel side as well.
Currently it all has to be hand-written down, hence my request for an example for using this with a real life example involving MVVM and UI decoupling.

[hkhmsft]

If any new actionable items arise, let us know either through a new Issue or directly on this thread. In the meantime, I'll be closing this Issue. Thanks once again for submitting your feedback!