GET /oauth/auz/grants/{GrantID}/authcomplete

Supports redirect from the identity provider after the resource owner's login with the identity provider is complete.

Note: These operations render the authorization page:

  • GET /oauth/auz/grants/provider/authcomplete{domainid:(/[^/]+?)?} (this operation) performs the same action using HTTP GET. You can use this if you do not need to maintain a static callback URI. The GrantID is a path parameter.
  • POST /oauth/auz/grants/provider/authcomplete{domainid:(/[^/]+?)?} performs the same action using HTTP POST. You can use this if you do not need to maintain a static callback URI and prefer to use HTTP POST. The GrantID is relayed in form URL-encoded POST content.

Corresponds to the Login Complete operation in the Login API, but relates to the resource owner's authentication with the Authorization Server, for the purposes of an OAuth grant, rather than authentication for the purpose of platform access.

Note: The operations in the Authorization Server Authorization Service are intended for use by the Resource Owner. There are corresponding operations in other services for other scenarios. Where applicable, use the corresponding operations in the OAuth Login service (Login Complete GET and POST).

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 a call to this operation.

Request URL


Sample request headers

GET /oauth/auz/grants/mehpkurlkhnn/auzcomplete HTTP/1.1
Host: {oauth-provider-hostname}
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

Sample request body

Not applicable.

Back to top

Request Headers

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

Header Description
Accept This operation does not validate the Accept header. Any value is accepted. The operation returns html, to support the browser.

Back to top

Request Parameters

Parameter Parm Type Data Type Required Description
GrantID Path string Required The unique ID for a specific instance of an OAuth grant.

Back to top


If successful, this operation returns HTTP status code 200, with the cookie.

Back to top

Sample Response

The sample response below shows successful completion of this operation. The user is redirected to the application's redirect URL.

Sample response headers

Set-Cookie: AtmoAuthToken_{oauth-provider-hostname}: TokenID%3D480a3a7c-240e-11e5-a1b9-8945fbb2b0eb%2Cclaimed_id%3Durn%3Aacmepaymentscorp%3Auser%3Aacmepaymentscorp
H70N6-QQKrhF5n9Lm5PYCKciKNWTSWVooauthRedirectInfoCookie: %7B%22accessTokenUrl%22%3A%22%2Fapi%2Fdevconsole%2Foauth%2Faccesstoken%22
OAuthToken_acmepaymentscorp: TokenID%3D57d30fc7-240e-11e5-a1b9-8945fbb2b0eb%2Cclaimed_id%3DLDAP_acmepaymentscorp%5Ceng100

Sample response body


Back to top

Response Headers

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

Header Description
Content-Type Returns text/html response.
OAuthToken_{OAuthProviderName} The OAuth cookie that identifies the logged-in user with the provider. Depending on the operation being used and the context, the authenticated user could be the resource owner, the administrator, the client app administration, or the OAuth Provider. The cookie is returned after logging in with the POST /oauth/login operation.

Back to top

Response Body

There is no response body. The important part of the response is the OAuth authentication cookie.

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
500 An error occurred processing the call.

More information about Akana OAuth API error messages.

Back to top

Related Topics