Skip to main content

Auth0

Before connecting Auth0 to AIGW, verify that your tenant supports the grant and client-authentication capabilities below.

Required capabilities​

Your Auth0 deployment would need an equivalent way to:

  • trust an external AIGW per-resource issuer and ES256 JWKS for the user assertion;
  • authenticate the AIGW merchant-AS client with asymmetric JWT client authentication, if using the private_key_jwt path;
  • accept the merchant issuer/audience used by AIGW;
  • define the same requested scopes;
  • resolve or provision a merchant user from the assertion sub;
  • issue an access token accepted by the merchant API.

Values from AIGW​

Use the AIGW Resource Reference page to collect:

Token exchange with a client secret​

For an Auth0 integration using token exchange, select token_exchange on the Resource and enter the merchant Client ID and Client secret. AIGW authenticates the token request with HTTP Basic and sends the signed user assertion as the subject token. With DevCLI (the aigw command-line tool), use --exchange.auth-method TOKEN_EXCHANGE and --exchange.client-secret. Configure the subject token type and audience to match your Auth0 token-exchange setup. See Token exchange request settings.

Validate your integration​

Verify that your Auth0 tenant and plan support the selected token-exchange flow and client authentication method. Configure how the external subject token is validated and mapped to a user before requesting access tokens.

After configuration, complete user authorization, retrieve the merchant access token, and call your merchant API. Sign-in success alone does not verify this integration.