Difference between revisions of "OpenID Connect Future"
From MgmtWiki
(→Context]) |
(→Context]) |
||
| Line 3: | Line 3: | ||
==Context]== | ==Context]== | ||
| − | [[OpenID Connect]] responded to the poor acceptance of OpenID 2.0 by leveraging the concept of "Front Channel Authentication". The method allows a user on a browser at a [[Relying Party]] to sign into an IdP without losing the context of the web site (ie the browser tab) that needs the [[Authentication]]. | + | [[OpenID Connect]] responded to the poor acceptance of OpenID 2.0 by leveraging the concept of "Front Channel Authentication". The method allows a user on a browser at a [[Relying Party]] (RP) to sign into an IdP and grant access to the RP without losing the context of the web site (ie the browser tab) that needs the [[Authentication]]. |
==References== | ==References== | ||
[[Category: Article]] | [[Category: Article]] | ||
Revision as of 10:04, 22 January 2021
Full Title or Meme
The advantages that lead to the large acceptance of OpenID Connect are being eroded. The future of the standard depends on how the OpenID responds to these challenges.
Context]
OpenID Connect responded to the poor acceptance of OpenID 2.0 by leveraging the concept of "Front Channel Authentication". The method allows a user on a browser at a Relying Party (RP) to sign into an IdP and grant access to the RP without losing the context of the web site (ie the browser tab) that needs the Authentication.
