Clarify auth capabilities on Enterprise page#888
Merged
Conversation
The "Basic authentication" row was read as HTTP Basic, and "Built-in IdP integration" implied OAuth/OIDC weren't available in community. Rename for accuracy, split token exchange into RFC 8693 (both) and Entra ID on-behalf-of (Enterprise-only), and align admonition copy to use "turnkey IdP integration" across the page and the landing page callout. Also fix Cedar casing, sentence-case the Enterprise platform components heading, and de-hyphenate "open source". Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
There was a problem hiding this comment.
Pull request overview
Updates ToolHive Enterprise documentation to reduce confusion in the auth & identity comparison content by clarifying terminology and tightening consistency with the style guide.
Changes:
- Reworded Enterprise landing-page
:::enterprisecallout to highlight “turnkey” identity provider support. - Updated the Enterprise auth/identity comparison table to clarify OAuth/OIDC auth, distinguish RFC 8693 token exchange vs. Entra OBO, and correct “Cedar” capitalization.
- Normalized heading capitalization and “open source” wording per the style guide.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/toolhive/index.mdx | Refines the Enterprise callout messaging on the ToolHive docs landing page. |
| docs/toolhive/enterprise.mdx | Clarifies auth/identity capability table rows and applies small style/wording fixes. |
Acronym was only used once on this page, so drop it entirely rather than introducing it just to abbreviate. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The auth & identity comparison table on the Enterprise page had two rows that prospects were reading the wrong way:
While in the area:
:::enterpriseadmonition on the docs landing page and the FAQ entry on the Enterprise page to use the same "turnkey IdP integration" framing.Type of change
Submitter checklist