Difference between revisions of "Revocation"
From MgmtWiki
(→Context) |
(→Solutions) |
||
| Line 11: | Line 11: | ||
==Solutions== | ==Solutions== | ||
| − | * Issue a [[Refresh Token]] that can be used by the [[Relying Party]] to acquire | + | * Issue a [[Refresh Token]] that can be used by the [[Relying Party]] to acquire a fresh access token with a short life time on demand. The IAP would then handle any [[Revocation]] for the user which would have no effect during that short life time. |
* Require the [[Authorization]] endpoint to verify liveness of the token before it authorizes actual access to the [[Resource]]. | * Require the [[Authorization]] endpoint to verify liveness of the token before it authorizes actual access to the [[Resource]]. | ||
Revision as of 10:14, 2 October 2018
Full Title or Meme
The problem of revoking a grant previously issued on behalf of a Subject which is a requirement of several privacy regulations.
Context
The collection of User Private Information by a Data Controller now necessitates the ability Authenticate the User under a wide range of challenges, like:
- Simplest of all the User needs to Authenticate from time to time and on a variety of devices under less than ideal conditions where passwords are mistyped and Alternate Authentication factors are lost or fail.
Problems
- Once a Bearer Token has been issued to a Relying Party by a Identifier or Attribute Provider there is no practical way to issue a Revocation that will guarantee success.
Solutions
- Issue a Refresh Token that can be used by the Relying Party to acquire a fresh access token with a short life time on demand. The IAP would then handle any Revocation for the user which would have no effect during that short life time.
- Require the Authorization endpoint to verify liveness of the token before it authorizes actual access to the Resource.
