Difference between revisions of "Relying Party Refresh"

From MgmtWiki
Jump to: navigation, search
(Created page with "This pattern IS TRACKING by the IdP of accesses by the user to the RP. That is considered to be a problem in the case of the mDL. It seems that the concept of RP Refresh is a...")
 
Line 1: Line 1:
This pattern IS TRACKING by the IdP of accesses by the user to the RP.
+
==Full Title or Meme==
That is considered to be a problem in the case of the mDL.
+
There are many reasons for a short duration [[Authorization]] ticket to be issued to users. Those cases typically require a refresh of the token without a heavy cognitive load on the user.
It seems that the concept of RP Refresh is a topic that should be considered independently of these various use cases as it needs to be controlled by the user agent in any case.
+
 
Perhaps an entirely separate standard for RP Refresh.
+
==Context==
 +
This pattern IS TRACKING by the IdP of accesses by the user to the RP.
 +
That is considered to be a problem in the case of the mDL.
 +
It seems that the concept of RP Refresh is a topic that should be considered independently of these various use cases as it needs to be controlled by the user agent in any case.
 +
Perhaps an entirely separate standard for RP Refresh.
  
 
==References==
 
==References==

Revision as of 12:00, 1 September 2022

Full Title or Meme

There are many reasons for a short duration Authorization ticket to be issued to users. Those cases typically require a refresh of the token without a heavy cognitive load on the user.

Context

This pattern IS TRACKING by the IdP of accesses by the user to the RP.
That is considered to be a problem in the case of the mDL.
It seems that the concept of RP Refresh is a topic that should be considered independently of these various use cases as it needs to be controlled by the user agent in any case.
Perhaps an entirely separate standard for RP Refresh.

References