Difference between revisions of "Identifying Returning Users"
From MgmtWiki
(→Context) |
(→Context) |
||
| Line 5: | Line 5: | ||
* [[Single Sign-On]] to multiple websites is a great improvement in any [[User Experience]] it was enabled by the use of [[Third Party]] [[Cookies]]. | * [[Single Sign-On]] to multiple websites is a great improvement in any [[User Experience]] it was enabled by the use of [[Third Party]] [[Cookies]]. | ||
* With the demise of [[Third Party]] Cookies, new methods for identifying returning users is more complex for a [[Relying Party]]. | * With the demise of [[Third Party]] Cookies, new methods for identifying returning users is more complex for a [[Relying Party]]. | ||
| + | * [[Native SSO]] allows sharing of [[Single Sign-On]] among native apps from the same vendor. | ||
==References== | ==References== | ||
[[Category: Identity]] | [[Category: Identity]] | ||
Revision as of 10:01, 1 October 2022
Full Title or Meme
Exploring the ways that a web site (aka a relying Party can determine if the current user of the site is known to that site from previous visits.
Context
- Single Sign-On to multiple websites is a great improvement in any User Experience it was enabled by the use of Third Party Cookies.
- With the demise of Third Party Cookies, new methods for identifying returning users is more complex for a Relying Party.
- Native SSO allows sharing of Single Sign-On among native apps from the same vendor.
