Difference between revisions of "Authentication UX"
From MgmtWiki
(→Problems) |
(→Version 2 of ODIC) |
||
Line 13: | Line 13: | ||
==Possible Solutions== | ==Possible Solutions== | ||
===Version 2 of ODIC=== | ===Version 2 of ODIC=== | ||
+ | * Disruptive innovation [https://www.gammabeyond.com/en/blog/why-companies-need-to-eat-their-children-a-comprehensive-guide-to-disruption/ requires any business to eat their own childern] or someone else will come along and do it first. | ||
+ | |||
===Focus on W3C=== | ===Focus on W3C=== | ||
Revision as of 13:57, 22 November 2020
Contents
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
- At least as good as UX
- 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.