GET /oauth/auz/authorize

Starts the authentication of the resource owner. On success, the user sees a login page based on the resource owner domain configured by the OAuth provider, so the user can complete authentication. Similar functionality to SSO Login in the Login service. Uses HTTP GET.

Note: there is a corresponding operation that performs the same action using HTTP POST: POST /oauth/auz/authorize. For information on why you might choose one or the other, see OAuth Operations: GET or POST? In general, GET is more popular for this operation.

Authorization Roles/Permissions: Anyone can run this operation.

This topic includes the following sections:

HTTP Method


Back to top



Back to top

Sample Request

The example below shows an authorization request.

Request URL #1


Request URL #2

OAuth 1.0a authorization request.


Sample request headers

Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Sample request body

Not applicable.

Request Headers

For general information on request header values, refer to HTTP Request Headers.

Header Description
Accept None required however the response is an HTML page.

Back to top

Request Parameters

Parameter Parm Type Data Type Required Description
oauth_token Query String Optional The OAuth 1.0 token; could be a GrantID.
oauth_verifier Query String Optional The OAuth 1.0 verifier; an internal value used as a temporary authorization code for the grant.
response_type Query String Required

OAuth 2.0: standard response_type parameter.

The response type value is derived based on the grant types.

client_id Query String Required OAuth 2.0: standard client_id parameter. The client identifier.
redirect_uri Query String Required OAuth 2.0: standard redirect_uri parameter. The redirect URI configured by the app. For more information, see OAuth Parameters.
scope Query String Optional OAuth 2.0: standard scope parameter. One or more scopes configured in the OAuth provider. Space separator for multiple scopes.
state Query String   OAuth 2.0: standard state parameter.
nonce Query String Optional

Used in the OpenID Connect implicit flow. Based on the response type, nonce might be required.

A nonce value for the openid request—a random string that is uniquely generated for each request.

response_mode Query String Optional The response will be returned based on the response_mode value. Supported values for the platform's OpenID Connect Relying Party domain: form_post, query, or fragment (see OpenID Connect Relying Party Response Mode values).

Back to top


If successful, this operation returns HTTP status code 200, with a grant that is created and returned as a path parameter. A successful response redirects the resource owner to the login page for authenticating and then authorizing scopes.

Back to top

Sample Response

The sample response below shows successful completion of this operation. The grant ID is returned in the Location header.

Sample response headers

HTTP/1.1 302 Found
Expires: Thu, 09 Jul 2015 13:57:23 GMT
Location: http://{oauth-provider-hostname}/oauthauz/#/grant/viit0bmhe2vl/authenticate

Sample response body

The response is a redirect back to the client URL as specified in the Location header.


Back to top

Response Headers

For general information on response header values, refer to HTTP Response Headers.

Header Description

The URL to which the resource owner is redirected after authentication is successful. The redirect URL, previously provided by the client to the identity provider and/or specified in the redirect_uri request parameter, is provided as the value for the Location header.

The GrantID is included in the Location header.

Back to top

Response Body

None. The response is a redirect of the user back to the client app's redirect_uri.

Back to top

Error Codes/Messages

If the call is unsuccessful an error code/message is returned. One or more examples of possible errors for this operation are shown below.

Item Value

Client id null.

Invalid_request. The request is missing a required parameter or includes an invalid parameter.

200 Invalid response type. The response type is not supported.

Nonce (required for hybrid grant types).

Nonce is a mandatory parameter for OpenID Connect implicit flow authentication requests.


Client ID not valid.

The client is not authorized to request an authorization code.


Scope not valid (if openid scope not present and corresponding response types are present).

The response type is not supported.


Scope not valid (if the scope configured is not present in the request).

The requested scope is invalid or missing.

302 Invalid redirect_uri.
500 An error occurred processing the call.

More information about Akana OAuth API error messages.

Back to top

Related Topics