Implicit Grant

Description

Implicit Grant flow is an alternative for Authorization Code flow. This flow just receives access_token in query string fragment instead of obtaining securecode. It's indented for client-side apps use in order to access an API, typically as Web SPA applications. For more detailed information, read OAuth 2.0 specification.

Authorization Endpoint

GET [base]/auth/authorize

Obtaining access token

Query Parameters

NameTypeDescription

state

string

a value used by the client to maintain state between the request and callback

scope

string

scope of the access request

redirect_uri

string

client redirect URI

client_id

string

client ID

response_type

string

value MUST be set to token

[redirect_uri]#access_token=YzI3ZjQ1M2MtYzFlYi00ZjI3LWI2MzgtOTQ0MWI0ZmIzZjBi&state=eyJoYXNoIjoiIy9pbXBsaWNpdC9iYXNpYyIsImZvcm0tZGF0YSI6eyJ0eXBlIjoiYmFzaWMiLCJiYXNpYyI6eyJjbGllbnQtaWQiOiJpbXAtY2xpZW50In19LCJmb3JtLXBhdGgiOiJpbXBsaWNpdC1wYWdlIn0%3D

After this request, the resource owner (user) will be redirected to Log-in/Sign-up page.

Next step is granting access to the client:

After granting access the user is redirected to the redirect_uri from the client configuration with access_token in query string fragment.

Example

POST /Client
Accept: text/yaml
Content-Type: text/yaml

id: imp-client
resourceType: Client
grant_types:
- implicit
auth:
  implicit:
    redirect_uri: http://localhost:3449/auth.html
curl -X GET \
  'http://localhost:8081/auth/authorize?
        state=example
        &client_id=imp-client
        &redirect_uri=http%3A%2F%2Flocalhost%3A3449%2Fauth.html
        &response_type=token'

Last updated

Change request #2416: