Difference between revisions of "Self-issued Reconnection"
From MgmtWiki
(→Context) |
(→Context) |
||
| Line 8: | Line 8: | ||
* Refresh Token | * Refresh Token | ||
* There category of [[Relying Party]] generated [[User Experience]] (UX): | * There category of [[Relying Party]] generated [[User Experience]] (UX): | ||
| − | ** Pure web UX - no user actions | + | ** Pure web UX - no user actions needed to enable the UX. |
** [[Progressive Web App]] - required user acceptance of app. | ** [[Progressive Web App]] - required user acceptance of app. | ||
** [[Native App]] = requires user to download and accept app. | ** [[Native App]] = requires user to download and accept app. | ||
Revision as of 16:58, 4 November 2021
Full Name or Meme
The experience for the user and the Relying Party over time requires a quick reconnection at the user's pleasure.
Context
- The two original reasons for browser Cookies are:
- The maintenance of a signed-in session.
- The reconnection of a user session when for a continuing relationship.
- Refresh Token
- There category of Relying Party generated User Experience (UX):
- Pure web UX - no user actions needed to enable the UX.
- Progressive Web App - required user acceptance of app.
- Native App = requires user to download and accept app.
References
- Currently supported by a browser-based Password Manager.
- See also the Vendor Relationship Manager
