Skip to content

OpenID Connect Implicit Client Profile

This section guides you through consuming an OpenID connect implicit client profile that is based on implicit flow. The following steps outline the flow according to the OpenID specification.

  1. The client prepares an authentication request containing the desired request parameters.
  2. The client sends the request to the authorization server.
  3. The authorization server authenticates the end-user.
  4. The authorization server obtains end-user consent/authorization.
  5. The athorization server sends the end-user back to the client with an ID token and, if requested, an access token.
  6. The client validates the ID token and retrieves the end-user's subject identifier.

The following parameters are mandatory and have to be included in the authorization request in order to execute this flow.


The following parameters have a different usage in the implicit flow vs its usage in the authorization code flow. - response_type - redirect_uri/callback_uri - nonce

scope Specifies the behaviour of the request.
Value: "openid"
client_id The OAuth 2.0 Client Identifier valid at the authorization server.

Determines which authorization processing flow is to be used, including what parameters are returned from the endpoints used.
Value: "id_token token" or "id_token"

  • id_token token:  The ID token is issued together with the access token.
  • id_token: Only the id token is returned and no access token is returned.
redirect_uri/callback_uri The URI which the authorization server should send the response to.
nonce Associates a client session with an ID Token to mitigate replay attacks. The value is passed through unmodified from the authentication request to the ID Token.

About oidc-scope-config.xml file

The oidc-scope-config.xml file enables grouping of claims that are bound to a scope value in OpenID Connect (OIDC). By default, the oidc-scope-config.xml file is located inside {IS_Home}/repository/conf/identity directory.

This file can be modified to add custom scopes or claims. When the server starts, these configurations are stored in the registry located in /oidc/ . You can customize claims or scopes from here as well. The returned clams from id token or user info endpoint will be decided based on both the requested scopes and requested claims.

When requesting for an OIDC token, you can specify a scope value that is bound to a set of claims in the oidc-scope-config.xml file. When sending that OIDC token to the userinfo endpoint, only the claims that are common to both the oidc-scope-config.xml and the service provider claim configuration, will be returned.

Related Topics

See the Implicit Client Profile with Playground topic to try out this flow with the playground sample for OAuth in WSO2 Identity Server.