Authentication UX

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.

Context

• 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.

Problems

• Especially with Federation Signing, the conn

Goals

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

• Disruptive innovation requires any business to eat their own childern or someone else will come along and do it first.
• Front channel communication had a long run, it may be time to look seriously at alternatives.

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.