4

I'm trying to use WebAccountManager for making login easier in a Windows 10 Universal Windows App (UWP).

It seems like the documentation around how to use WebAccountManager is somewhat lacking. Are Microsoft Account (MSA) and AAD the only WebAccountProvider implementations that come out of the box?

Did anyone have any luck making this work, and have code to share?

Thanks!

  • I guess you're looking into the wrong namespace. Take a look at this namespace: https://msdn.microsoft.com/en-us/library/windows/apps/windows.security.authentication.web.aspx – Stefan Over Sep 01 '15 at 19:25
  • Great! Based on Channel9 and MSDN I thought the goal was to have it replaced by [WebAccountManager](https://msdn.microsoft.com/en-us/library/windows/apps/windows.security.authentication.web.provider.webaccountmanager.aspx) which leverages the existing accounts associated with Windows, but WebAuthenticationBroker would do the trick :) Thanks! – user2844291 Sep 01 '15 at 20:50

1 Answers1

0

The identity providers unsupported by WebAccountManager can be added to the authentication prompt using the WebAccountProvider class.

Getting the access token of the new provider is the responsibility of the WebAuthenticationBroker class.

Note: You may also want to use the newer MSAL.net library instead. It appears to be equivalent to the WebAccountManager and there's also a simple UWP code example available.

Jan Lenoch
  • 79
  • 2
  • 8