Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Name and Last Access #13

Closed
GregTurner opened this issue Jan 21, 2013 · 1 comment
Closed

App Name and Last Access #13

GregTurner opened this issue Jan 21, 2013 · 1 comment

Comments

@GregTurner
Copy link
Contributor

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.

@dickhardt
Copy link
Owner

App name is managed by the Registrar. Each RS gets it from the Registrar. Use first one you see.

Last Access to show user is which ever Last Access is latest.

On Jan 20, 2013, at 4:23 PM, GregTurner notifications@github.com wrote:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants