https://docs.protegrity.com/aiteam-edition/docs/ai_security/fedx/usage/Recent content in Usage onHugoenhttps://docs.protegrity.com/aiteam-edition/docs/ai_security/fedx/usage/user_creation/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/aiteam-edition/docs/ai_security/fedx/usage/user_creation/<p>AI Gateway accepts a verified JWT as the caller&rsquo;s identity. Choose one of these identity setups:</p> <ul> <li>Use a PPC user when your deployment uses PPC authentication.</li> <li>Configure an external identity provider (IdP) when callers authenticate through an issuer such as Keycloak or Microsoft Entra ID.</li> </ul> <p>Regardless of issuer, send the identity JWT to the gateway in the <code>x-user-auth</code> request header. The gateway validates it against the configured IdP trust registry.</p>https://docs.protegrity.com/aiteam-edition/docs/ai_security/fedx/usage/using/Mon, 01 Jan 0001 00:00:00 +0000https://docs.protegrity.com/aiteam-edition/docs/ai_security/fedx/usage/using/<p>Configure client applications to send requests through the AI Gateway. The gateway API base URL is <code>&lt;GATEWAY_HOST&gt;/pty/federated-guardrails/v1</code>; the client library appends its endpoint path.</p> <p>Every request must include the caller&rsquo;s verified identity JWT in <code>x-user-auth</code>. The optional <code>x-team-id</code> header selects a profile according to the deployment&rsquo;s routing configuration. For example, the sample policy routes <code>cs-bot</code> to <code>simple-protection</code>, <code>dps-bot</code> to <code>dps-protection</code>, <code>dpsl-bot</code> to <code>dpsl-protection</code>, <code>sdc-bot</code> to <code>sdc-protection</code>, and <code>gai-bot</code> to <code>gai-protection</code>; requests without a matching header use the configured default profile.</p>