Authentication UX

From MgmtWiki
Revision as of 14:04, 22 November 2020 by Tom (talk | contribs) (Problems)

Jump to: navigation, search

Full Title or Meme

The successful Authentication schems, like OpenID Connect have been those that provide a good User Experience. Schemes that impeded the user work flow the least.


  • The major feature of OpenID Connect (OIDC) was its ability to operate on the "Front Channel" so that he user browser context was maintained and the user could get on with the work at hand.
  • The browser makers are currently completing on which one provides the best privacy considerations. As the security of the user information is increased, it inevitably impedes the flows that worked well for OIDC.


  • Especially with Federation Signing, the connections used between different browser widows has make the user extence good, but is indistinguishable from user tracking which the browser manufacturers have vowed to drastically reduce.
    • Web ID wants to know if a web site is acting as an IdP.
    • IsLoggedOn (and its children like IsAutenticated).
  • Any Self-issued Identity Provider (SIOP) requires some method to authentication while preserving the user work flow. The existing techniques available from the browser do not do that.


  1. At least as good as UX
  2. Improve user Privacy by increasing the security of both user data and user attention.

Possible Solutions

Version 2 of ODIC

Focus on W3C

  • Wether version 2 is started or not, it is important to help the W3C, and the browser folk in particular, to work with OpenID and DIF to create a win-win solution.