[pull] master from DataDog:master

hugo/assets/scripts/config/regions.config.js

@@ -845,6 +845,28 @@ export default {
     uk1: 'https://mcp.uk1.datadoghq.com/v1/mcp',
     gov: 'The MCP Server endpoint for GOV is not supported.'
   },
+  mcp_xaa_resource_url: {
+    us: 'https://mcp.datadoghq.com/v1/mcp',
+    us3: 'https://mcp.us3.datadoghq.com/v1/mcp',
+    us5: 'https://mcp.us5.datadoghq.com/v1/mcp',
+    eu: 'https://mcp.datadoghq.eu/v1/mcp',
+    ap1: 'https://mcp.ap1.datadoghq.com/v1/mcp',
+    ap2: 'https://mcp.ap2.datadoghq.com/v1/mcp',
+    uk1: 'https://mcp.uk1.datadoghq.com/v1/mcp',
+    gov2: 'Cross-App Access is not supported for US2-FED.',
+    gov: 'Cross-App Access is not supported for US1-FED.'
+  },
+  mcp_xaa_issuer_url: {
+    us: 'https://mcp.datadoghq.com/v1/mcp',
+    us3: 'https://mcp.us3.datadoghq.com/v1/mcp',
+    us5: 'https://mcp.us5.datadoghq.com/v1/mcp',
+    eu: 'https://mcp.datadoghq.eu/v1/mcp',
+    ap1: 'https://mcp.ap1.datadoghq.com/v1/mcp',
+    ap2: 'https://mcp.ap2.datadoghq.com/v1/mcp',
+    uk1: 'https://mcp.uk1.datadoghq.com/v1/mcp',
+    gov2: 'Cross-App Access is not supported for US2-FED.',
+    gov: 'Cross-App Access is not supported for US1-FED.'
+  },
   cursor_mcp_install_deeplink: {
     us: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us1&config=eyJ1cmwiOiJodHRwczovL21jcC5kYXRhZG9naHEuY29tL2FwaS91bnN0YWJsZS9tY3Atc2VydmVyL21jcD90b29sc2V0cz1vbmJvYXJkaW5nIiwidHlwZSI6Im9hdXRoIn0=',
     us3: 'cursor://anysphere.cursor-deeplink/mcp/install?name=datadog-onboarding-us3&config=eyJ1cmwiOiJodHRwczovL21jcC51czMuZGF0YWRvZ2hxLmNvbS9hcGkvdW5zdGFibGUvbWNwLXNlcnZlci9tY3A/dG9vbHNldHM9b25ib2FyZGluZyIsInR5cGUiOiJvYXV0aCJ9',

hugo/config/_default/menus/main.en.yaml

@@ -10409,6 +10409,11 @@ menu:
       parent: organization_settings
       identifier: account_management_org_settings_smtp_configuration
       weight: 309
+    - name: Cross-App Access
+      url: account_management/org_settings/cross_app_access
+      parent: organization_settings
+      identifier: account_management_org_settings_cross_app_access
+      weight: 310
     - name: Access Control
       url: account_management/rbac/
       parent: account_management

hugo/config/_default/params.yaml

@@ -336,6 +336,7 @@ unsupported_sites:
   continuous_integration: [gov,gov2]
   correlation: [gov,gov2] #Event management correlation
   coterm: [gov,gov2]
+  cross_app_access: [gov,gov2]
   csm_jira: [us,us3,us5,eu,ap1,ap2,uk1]
   cpp_log_collection: [gov,gov2]
   data_jobs: [gov,gov2]

hugo/content/en/account_management/org_settings/cross_app_access.md

@@ -0,0 +1,198 @@
+---
+title: Cross-App Access
+description: Configure Okta Cross-App Access so AI agents can call the Datadog API on behalf of users authorized in Okta.
+algolia:
+  tags: ["cross-app access", "XAA", "Okta", "AI agent", "MCP", "ID-JAG"]
+further_reading:
+    - link: '/mcp_server/setup/'
+      tag: 'Documentation'
+      text: 'Set up the Datadog MCP Server'
+    - link: '/account_management/org_settings/mobile_third_party_access/'
+      tag: 'Documentation'
+      text: 'Mobile and Third-Party Access'
+    - link: '/account_management/saml/'
+      tag: 'Documentation'
+      text: 'Configure SAML single sign-on'
+---
+
+{{< callout url="#" btn_hidden="true" header="false">}}
+  Cross-App Access is in Preview. Okta gates access to the preview and enables it for your tenant, and the Okta capabilities this setup depends on are not generally available yet. Any Datadog organization can enable Cross-App Access on the Datadog side today.
+{{< /callout >}}
+
+## Overview
+
+Cross-App Access (XAA) lets AI agents call the Datadog API on behalf of users your organization already authorized in Okta. Without it, every user authorizes the agent individually through a browser consent screen. With it, your Okta administrator grants that access once, centrally, and users skip the per-user consent step.
+
+Okta issues the agent a short-lived token called an ID-JAG (Identity Assertion JWT Authorization Grant). The agent presents this token to Datadog, and Datadog exchanges it for an access token owned by the user who initiated the call. Because Okta mints the token, your administrators grant and revoke Datadog access for AI agents from Okta.
+
+In Preview, Cross-App Access supports Okta as the only identity provider and Claude as the only agent.
+
+## Values you exchange
+
+Setup moves values in both directions between Datadog and Okta. Two of them are issuer URLs that name different systems, so confirm you enter each one in the correct place.
+
+| Value                               | Direction       | Where you enter it                                                                        |
+| ----------------------------------- | --------------- | ----------------------------------------------------------------------------------------- |
+| Datadog organization UUID           | Datadog to Okta | Datadog application in Okta, {{< ui >}}Resource Server{{< /ui >}} tab, {{< ui >}}Audience/tenant ID{{< /ui >}}              |
+| Claude client ID                    | Datadog to Okta | Okta AI Agent, {{< ui >}}Resource Connection{{< /ui >}}, {{< ui >}}Client ID at resource{{< /ui >}}                         |
+| Datadog resource URL and issuer URL | Datadog to Okta | Datadog application in Okta, {{< ui >}}Resource Server{{< /ui >}} tab, {{< ui >}}Resource URL{{< /ui >}} and {{< ui >}}Issuer URL{{< /ui >}} |
+| Okta tenant issuer URL              | Okta to Datadog | Datadog API, `mcp_cross_app_access_issuer_url` org config                                 |
+
+## Prerequisites
+
+- Your organization uses Okta for SAML single sign-on to Datadog. Cross-App Access resolves users through your existing SAML connection, so it does not work without one. See [Configure SAML single sign-on](/account_management/saml/).
+- Each user who uses Claude exists in your Datadog organization and is assigned to both the Claude application and the Datadog application in Okta.
+- Configuration happens through the Datadog API, so you need the `org_management` permission and a [Personal Access Token](/account_management/personal-access-tokens/) (PAT), used as `DD_TOKEN` in the examples.
+- Your Okta tenant has the {{< ui >}}AI Agent Identity Assertion{{< /ui >}} and {{< ui >}}Agent to Agent Connections{{< /ui >}} Early Access features enabled, and you have Okta Super Administrator access.
+
+## Configure Cross-App Access in Datadog
+
+Complete the Datadog steps before the Okta steps. Datadog rejects tokens for organizations that have not enabled Cross-App Access, so configuring Okta first produces failures until you finish here.
+
+### Enable Cross-App Access
+
+Set the `mcp_cross_app_access_enabled` org config to `true`. This applies to your whole organization. The `org_management` permission is required to authorize the call.
+
+```shell
+curl -X PATCH "{{< region-param key="dd_api" >}}/api/v2/org_configs/mcp_cross_app_access_enabled" \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer ${DD_TOKEN}" \
+  -d '{
+    "data": {
+      "type": "org_configs",
+      "attributes": {
+        "value": true
+      }
+    }
+  }'
+```
+
+To turn Cross-App Access off later, send the same request with `"value": false`.
+
+### Set your Okta issuer URL
+
+Datadog derives the location of the token signing keys from this value, so it must be exact.
+
+```shell
+curl -X PUT "{{< region-param key="dd_api" >}}/api/v2/login/org_configs/mcp_cross_app_access_issuer_url" \
+  -H "Content-Type: application/json" \
+  -H "Authorization: Bearer ${DD_TOKEN}" \
+  -d '{
+    "data": {
+      "type": "org_config",
+      "attributes": {
+        "issuer_url": "https://<YOUR_OKTA_SUBDOMAIN>.okta.com"
+      }
+    }
+  }'
+```
+
+The issuer URL must meet all of the following, or the request returns `400`:
+
+- Use `https`.
+- Use a subdomain of `.okta.com`, `.oktapreview.com`, or `.okta-emea.com`. Datadog rejects the apex domain, so `example.okta.com` works and `okta.com` does not work.
+
+Sending an empty string unsets the issuer and stops Datadog from accepting tokens.
+
+### Get your organization UUID
+
+Okta sends this value as the `aud_tenant` claim, which tells Datadog which organization a token targets when several organizations share one Okta tenant. It is not the same as the company ID that Okta asks for elsewhere.
+
+To get your organization UUID, call [{{< region-param key="dd_api" >}}/api/v2/current_user](https://app.datadoghq.com/api/v2/current_user) with an active session in the target organization. The UUID is the `id` of the `orgs` entry in the `included` array.
+
+### Note the Claude client ID
+
+Claude uses one OAuth client ID in every Datadog organization:
+
+{{< code-block lang="text" >}}
+391e6845-8153-4de1-bbf0-c1b6ef7fdc14
+{{< /code-block >}}
+
+You enter this in Okta as {{< ui >}}Client ID at resource{{< /ui >}}.
+
+## Finish the setup in Okta
+
+Complete the setup in the Okta Admin Console as a Super Administrator. This section lists the values Datadog expects and the Okta fields they belong in. See [Okta's Cross-App Access documentation](https://help.okta.com/oie/en-us/content/topics/apps/apps-cross-app-access.htm) for more details. 
+
+### Configure the Datadog application as a resource server
+
+On your Datadog application, open the {{< ui >}}Resource Server{{< /ui >}} tab and enable {{< ui >}}Cross-app access (XAA){{< /ui >}}. Set the following fields.
+
+{{< site-region region="us,us3,us5,eu,ap1,ap2,uk1" >}}
+<p>The values below match your selected <a href="/getting_started/site/">Datadog site</a> ({{< region-param key="dd_site_name" >}}). To see the values for another site, use the {{< ui >}}Datadog Site{{< /ui >}} selector on the right side of this page.</p>
+<table>
+<thead><tr><th>Okta field</th><th>Value</th></tr></thead>
+<tbody>
+<tr><td>{{< ui >}}Resource URL{{< /ui >}}</td><td>{{< region-param key="mcp_xaa_resource_url" code="true" >}}</td></tr>
+<tr><td>{{< ui >}}Issuer URL{{< /ui >}}</td><td>{{< region-param key="mcp_xaa_issuer_url" code="true" >}}</td></tr>
+<tr><td>{{< ui >}}Audience/tenant ID{{< /ui >}}</td><td>Your Datadog organization UUID</td></tr>
+</tbody>
+</table>
+{{< /site-region >}}
+
+The issuer URL identifies the Datadog authorization server, not the token endpoint. Okta writes it into the `aud` claim of the tokens it issues, and Datadog accepts a token only when that claim matches.
+
+**Note**: Changing the issuer URL later requires deleting and recreating the resource connection described in [Connect Claude to the Datadog application](#connect-claude-to-the-datadog-application).
+
+### Register Claude as an AI Agent
+
+Create an AI Agent entry for Claude in Okta, then exchange keys with Anthropic. Anthropic signs the requests Okta receives, so Okta needs Anthropic's public key before it issues any token.
+
+1. Create the AI Agent entry for Claude.
+2. Assign owners to the agent. Okta requires an owner before you can activate it.
+3. Send the AI Agent ID that Okta generates to Anthropic.
+4. Add the public key that Anthropic returns to the AI Agent entry, on the {{< ui >}}Credentials{{< /ui >}} tab.
+
+Until the public key is in place, token exchange fails even though every other value is correct. This exchange is manual, so start it early.
+
+### Connect Claude to the Datadog application
+
+On the Claude AI Agent, add the Claude SAML application as a delegated caller, then connect the agent to your Datadog application.
+
+1. On the {{< ui >}}Delegations{{< /ui >}} tab, add the Claude SAML application as a caller.
+2. On the {{< ui >}}Resource connections{{< /ui >}} tab, add a resource connection. Select {{< ui >}}Application{{< /ui >}} as the resource type, then select your Datadog application.
+3. Set the following fields.
+
+   | Okta field                | Value                                                                                                |
+   | ------------------------- | ---------------------------------------------------------------------------------------------------- |
+   | {{< ui >}}Client ID at resource{{< /ui >}} | `391e6845-8153-4de1-bbf0-c1b6ef7fdc14`                                                               |
+   | {{< ui >}}Scope Condition{{< /ui >}}       | {{< ui >}}Allow all{{< /ui >}}, the only supported value. See [Control scopes in Datadog](#control-scopes-in-datadog) |
+
+4. Activate the agent from the {{< ui >}}Actions{{< /ui >}} menu.
+
+## Control scopes in Datadog
+
+{{< ui >}}Allow all{{< /ui >}} is the only supported {{< ui >}}Scope Condition{{< /ui >}} for Cross-App Access. Set it in Okta, then restrict what Claude reaches from Datadog.
+
+Okta does not filter scopes. With {{< ui >}}Allow all{{< /ui >}}, Okta copies whatever Claude requests into the token, which makes Datadog the enforcement point.
+
+<div class="alert alert-warning">Do not enter a list of scopes in Okta. Okta rejects any token request that contains a scope outside the list, so the integration fails with an error instead of falling back to narrower access.</div>
+
+To set the scopes Claude is allowed:
+
+1. Navigate to [{{< ui >}}Organization Settings > Mobile and Third-Party Access{{< /ui >}}](https://app.datadoghq.com/organization-settings/mobile-third-party-access).
+2. Select the Claude application, then select the {{< ui >}}Scopes{{< /ui >}} tab.
+3. Use the {{< ui >}}Allowed{{< /ui >}} checkbox for each scope to control what Claude reaches.
+4. Click {{< ui >}}Enable{{< /ui >}} to save.
+
+Adding or removing a scope affects every user in your organization, and removing a scope revokes existing authorizations that rely on it. See [Application Scope Management](/account_management/org_settings/mobile_third_party_access/#application-scope-management).
+
+A scope that is not allowed in Datadog is never granted, regardless of what the token requests.
+
+## Add Datadog as a connector in Claude
+
+1. In Claude, click the {{< ui >}}+{{< /ui >}} icon at the bottom of any prompt, then click {{< ui >}}Add Connector{{< /ui >}}.
+2. Find **Datadog** in the directory and enable the connector.
+3. Complete the sign-in flow when prompted.
+
+Use the Datadog connector from the directory, not a custom connector.
+
+## Verify the configuration
+
+Sign in to Claude as a user assigned to both Okta applications, then run a request that calls Datadog. A successful call confirms the full path: Okta issues the token, Datadog accepts it, and Datadog resolves the user.
+
+If a user signed in before you enabled Cross-App Access, have them sign out of Claude and sign back in through Okta. Sessions established earlier lack the identity token the agent needs.
+
+## Further reading
+
+{{< partial name="whats-next/whats-next.html" >}}