-
Notifications
You must be signed in to change notification settings - Fork 0
Cross Channel Auth
Mike Varley edited this page Jul 31, 2020
·
2 revisions
Not all Clients are Web Browser based Applications. Not all AS are Web Browser based Applications.
In a Client authorization request, the Client needs to express to the AS its user interaction capabilities. During a Client authorization, the AS may need to indicate to a Client the best way to direct an End-User for the authorization interaction.
For Example (1)
Client -> AZ: I am a Client running on a Smart TV with no keyboard input.
AZ -> Client: no problemo, here is a Short Code the End-User can enter into my website on another device.
For Example (2)
Client -> AZ: I am a web browser app on a desktop and I want to auth the End-User
AZ -> Client: Auth is done in a mobile app. Here is a universal link/code the End-User can use to get to the App.