Skip to main content

Auth0

The supplied source material does not contain a verified Auth0 console walkthrough for this AIGW flow. This page therefore records the integration contract you need to reproduce in Auth0 without inventing product-specific clicks or claiming support that was not tested.

Required capabilities​

Your Auth0 deployment would need an equivalent way to:

  • trust an external AIGW per-resource issuerPer-resource issuerThe AIGW authorization server dedicated to one Resource, at /<RESOURCE_ID> on the AIGW API host. Agents discover it; merchants trust it. and ES256 JWKSJWKSJSON Web Key Set: a published set of public keys used to verify JWT signatures. for the user assertion;
  • authenticate the AIGW merchant-AS client with asymmetric JWT client authentication, if using the supplied 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 ResourceResourceThe downstream system registered in a Project. Its kind (Token exchange or OAuth client) decides the role AIGW plays. Reference page to collect:

  • per-resource issuer;
  • per-resource JWKS URL;
  • client ID;
  • resource indicator;
  • requested scopes.

Before committing to this path​

Verify in your Auth0 tenant and plan that the required external JWT authorization-grant/token-exchange pattern and JWT client authentication are supported for your use case. The supplied AIGW materials do not establish those product/plan details.

If you validate the exact Auth0 setup, this page can be expanded into the same screenshot-backed procedure as the Keycloak guide.