You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the agent is retrieving the authorizations during Review Authorizations, it goes to the registrar passing previously known RS ID(s). In response, the Agent get tokens to call all the RS. The RS provides names of Apps and last access time among other things.
If an App is present in more than one RS response, in theory there could be a conflict between App Name and Last Access. How to handle? Warn user, provided both, or ignore?
Low priority.
The text was updated successfully, but these errors were encountered:
When the agent is retrieving the authorizations during Review Authorizations, it goes to the registrar passing previously known RS ID(s). In response, the Agent get tokens to call all the RS. The RS provides names of Apps and last access time among other things.
If an App is present in more than one RS response, in theory there could be a conflict between App Name and Last Access. How to handle? Warn user, provided both, or ignore?
Low priority.
—
Reply to this email directly or view it on GitHub.
When the agent is retrieving the authorizations during Review Authorizations, it goes to the registrar passing previously known RS ID(s). In response, the Agent get tokens to call all the RS. The RS provides names of Apps and last access time among other things.
If an App is present in more than one RS response, in theory there could be a conflict between App Name and Last Access. How to handle? Warn user, provided both, or ignore?
Low priority.
The text was updated successfully, but these errors were encountered: