Single Sign-On with Secure Authentication

Play Single Sign-On with Secure Authentication
Sign in to queue

Description

Most apps today require users to sign in to online services to provide functionality, personalization, or both. These services cover a wide range of offerings, such as those provided by Microsoft or other online providers. This session will cover the new authentication features, APIs and experiences available in Windows 10 that help app developers and online service providers deliver a great experience to their customers.

Day:

2

Session Type:

Breakout

Code:

2-709

Room:

Room 2005

Embed

Download

The Discussion

  • User profile image
    Niner93302

    Is this session video going to be made available?

  • User profile image
    Niner93302

    Thanks. Better late than never :)

  • User profile image
    raulp

    I was watching this session and have a few questions. Mostly regarding to security concerns in using the broker. Also please note the link to download SDK sample in the slides is no longer working.

    1. How is the WebAccountProvider is secured so a rogue application can't register for my account provider. Or at very least can client apps specify they want the broker hosted only by a specific AppPackageFamilyName?
    2. Can client applications discover the AppPackageFamily name of application hosting the provider?
    3. Is the ClientId property in WebTokenRequest same as client's AppPackageFamilyName? Would like to validate the app has access to broker.
    4. Does user deleting account also delete provider, or only account information? Want to confirm that as long as app hosting the provider is installed that provider will remain registered.

    Thank You.

Add Your 2 Cents