Skip to content

Fortified IDDocs

Authorization code

Configuration and usage guidance for Authorization code in Fortified ID Access.

For the authorization code flow, calling the token endpoint is the second step of the flow. HTTP POST is used for the token endpoint.

Example: http://127.0.0.1:8080/oidc/tenant1/token-endpoint

These parameters must be posted as a part of the URL-encoded form values.

ParameterDescriptionMandatory
codeThe value that was returned from the authorization endpoint.true
client_idIdentifies the client and must match the value configured in FortifiedID Integrity.false
client_secretAuthenticates the client and must match the value configured in FortifiedID Integrity.false
grant_typeSupported value is authorization_code.false
redirect_uriSpecifies the redirect location. It must match the value configured in FortifiedID Integrity.true
code_verifierRequired if code_challenge was used in the authorization endpoint request.false

The token endpoint accepts either:

  • client authentication with client_secret_basic or client_secret_post
  • PKCE with code_verifier

If code_verifier is present, client_secret is not required. If neither client authentication nor PKCE is used, the request is rejected.

When PKCE or client_secret_post is used, client_id must still be included so the relying party can be resolved.

FortifiedID Integrity supports the following methods:

Method Description
client_secret_basic Provide 'clientid' and 'client_secret' in the Authorization header. (Basic auth)
client_secret_post Provide 'clientid' and 'client_secret' as parameters in the POST request body.
none For PKCE use. Provide the 'code_verifier' as a parameter in the POST request body.