Difference between revisions of "Authentication UX"

From MgmtWiki
Jump to: navigation, search
(Created page with "==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...")
 
(Context)
Line 5: Line 5:
 
* 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 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.
 
* 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
  
 
==References==
 
==References==

Revision as of 12:12, 22 November 2020

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

References