[pull] master from DataDog:master - #1094
Merged
Merged
Conversation
…38908) * Add Cross-App Access (XAA) setup documentation for Okta Documents how admins configure Okta Cross-App Access so AI agents can call the Datadog API on behalf of users authorized in Okta, without a per-user consent screen. Covers the Datadog-side configuration, the values exchanged in each direction with Okta, scoping through Application Scope Management, the Okta-side resource server and AI agent setup, and troubleshooting. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Use Datadog site parameters for Cross-App Access URLs Replace the hardcoded per-site URL table with region params so the page shows the values for the reader's selected Datadog site. Adds mcp_xaa_resource_url and mcp_xaa_issuer_url to regions.config.js, covering US1, US3, US5, EU, AP1, AP2, and UK1, and marks the feature unsupported on the government sites. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Reduce Okta click-path to field-level values Replace the step-by-step Okta console walkthrough with tables of the values Datadog expects and the Okta fields they belong in, and point to Okta's documentation for the full procedure. Keeps the Datadog-owned values authoritative while reducing drift against Okta's UI. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Remove troubleshooting section Also drops the sentence pointing to the troubleshooting table from the connector section. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Remove agent-side connector setup steps The connector configuration belongs in the agent vendor's documentation. Verify the configuration now points there instead. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Drop remaining connector reference from Verify section Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * Address review feedback on Cross-App Access setup - Correct resource URL values to include the /v1/mcp path - Clarify that scope restrictions apply in either Datadog or Okta - Describe the audience value as the organization ID - Reword the token control sentence in the overview * Document API-based Cross-App Access setup for the first release - Replace the organization settings steps with the org config API calls - Scope the page to Claude and give its shared client ID - Add the Okta AI Agent key exchange and the Claude connector step - Note that an interface is planned for a future release - Remove the settings screenshot, which has no equivalent in this release * Generalize Cross-App Access overview and recommend access tokens - Describe Cross-App Access in terms of AI agents, and state the Preview support scope separately - Recommend Personal and Service Access Tokens over API and application key pairs, and use the Authorization header in the API examples * Move Cross-App Access scope guidance to the Okta connection step - Explain scope control where the Okta Scope Condition field appears, instead of in a separate section - Drop the redundant issuer URL host rule and the Org Config API link * Use inline links inside site-region blocks Reference-style links do not resolve inside the shortcode, so they rendered as literal text on the page. * Use HTML inside site-region blocks on Cross-App Access page On account_management pages the site-region shortcode outputs its inner content without rendering markdown, so the table and links rendered as literal text. * Correct how Okta handles Cross-App Access scopes Okta admits or rejects a token request rather than narrowing it, so prescribe Allow all in Okta and control scopes from Datadog. * Trim the Cross-App Access scope section Remove design rationale that does not affect the setup steps. * State that Allow all is the only supported Okta Scope Condition * Update the Claude OAuth client ID * Update content/en/account_management/org_settings/cross_app_access.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update content/en/account_management/org_settings/cross_app_access.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update content/en/account_management/org_settings/cross_app_access.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Update content/en/account_management/org_settings/cross_app_access.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> * Match the Okta AI Agent setup order and add the owners step Okta requires an owner before an agent can be activated, and its console takes the delegated caller before the resource connection. * Explain why the Okta resource type is Application * Align Cross-App Access page with docs conventions - Use the callout shortcode for the Preview notice - Promote the scopes section to a heading the table of contents shows - List the prerequisites * Restore lost sections and fix Cross-App Access page rendering - Restore the verification and further reading sections, the scopes warning, and the Name ID and credential prerequisites - Use HTML inside site-region blocks, where markdown is not rendered - Point at the Datadog connector in Claude instead of a custom connector * Simplify the Claude connector instructions * Note that Okta gates the Cross-App Access preview * Simplify the Cross-App Access overview * Shorten the credential prerequisite * Remove the Name ID prerequisite * Add a copy button to the Claude client ID * Trim the Claude connector note * Apply documentation review feedback - Register cross_app_access in unsupported_sites for the site banner - Remove the How it works section and the redundant gov notice - Promote the scopes section to a top-level heading - Wrap Okta and Datadog UI strings in the ui shortcode * Note Okta capabilities are not yet generally available --------- Co-authored-by: Anthony Dagneaux <anthony.dagneaux@datadoghq.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )