:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
fix(oauth): drop the beta label from id-jag in auth.md (#129378)
Rafael Audiberta42ca365e849
diff --git a/posthog/templates/auth_md.md b/posthog/templates/auth_md.mdindex ba0dae0a01e6..162d35dc1f35 100644--- a/posthog/templates/auth_md.md+++ b/posthog/templates/auth_md.md@@ -12,9 +12,9 @@ PostHog is an open-source platform for product analytics, session replay, featur- OAuth 2.0: standard authorization-code flow for an app acting on behalf of a user. See https://posthog.com/docs/api/oauth- Personal API keys: long-lived keys for scripts and server-to-server use. See https://posthog.com/docs/api#authentication-## Agent registration via ID-JAG (Scale and Enterprise, beta)+## Agent registration via ID-JAG (Scale and Enterprise)-Available to organizations on the Scale or Enterprise platform add-on that have XAA configured. It is in beta, so most clients should use one of the options above. With it configured, an agent presents an [ID-JAG](https://xaa.dev) identity assertion (`identity_assertion`) to the token endpoint using the JWT-bearer grant (`urn:ietf:params:oauth:grant-type:jwt-bearer`) and receives a scoped, short-lived OAuth access token bound to the user. The agent must also authenticate as a registered client, with a client secret or `private_key_jwt`, and the ID-JAG's `client_id` must name that client. See https://posthog.com/docs/settings/id-jag+Available to organizations on the Scale or Enterprise platform add-on that have XAA configured. It only works once an organization admin sets up XAA, so most clients should use one of the options above. With it configured, an agent presents an [ID-JAG](https://xaa.dev) identity assertion (`identity_assertion`) to the token endpoint using the JWT-bearer grant (`urn:ietf:params:oauth:grant-type:jwt-bearer`) and receives a scoped, short-lived OAuth access token bound to the user. The agent must also authenticate as a registered client, with a client secret or `private_key_jwt`, and the ID-JAG's `client_id` must name that client. See https://posthog.com/docs/settings/id-jag- Identity endpoint: `{{ base_url }}/oauth/token/`- Assertion type: `urn:ietf:params:oauth:token-type:id-jag`