User can authorize the same application multiple times

[angelaraya]

If the user already has an authorization for http://projectr.on, it is possible for the application to trigger a new authorization request flow. Instead the client should either:

• redirect to the existing authorization screen, where the user can edit the existing authorization
• be informed of the issue and sent to the home screen
• return the user immediatly to the application indicating that an authorization already exists

[elf-pavlik]

• redirect to the existing authorization screen, where the user can edit the existing authorization

Do you see a need to handle new authorizations and re-authorizations differently? Besides showing to the user existing authorization and presetting any choices based on the existing authorization.