Repository navigation
docs(fleet): document registering an OAuth provider for manual MCP OAuth - #4922
Closed
Rafid S (rx5ad) wants to merge 1 commit into
Closed
Rafid S (rx5ad) wants to merge 1 commit into
Rafid S (rx5ad) wants to merge 1 commit into
Conversation
Manual OAuth for remote MCP servers required a pre-registered, PKCE-enabled OAuth provider, but the docs never explained where to register one or what fields it needs. Add a Register an OAuth provider section (Settings > OAuth providers) covering the fields, the required redirect URL, and the PKCE requirement, and clarify when to choose Auto vs Manual.
Contributor
|
Thanks for opening a docs PR, Rafid S (@rx5ad)! When it's ready for review, please add the relevant reviewers:
|
Contributor
|
Mintlify preview branch generated: Site preview: https://langchain-5e9cc07a-preview-rafidf-1784156729-8f496fa.mintlify.site Important Preview links may take a few minutes to start working while the deployment finishes. Changed documentation pages (preview deep links): |
Lauren Hirata Singh (lnhsingh)
added a commit
that referenced
this pull request
Oct 15, 2026
Client credentials is a provider grant type under OAuth 2.1 (Manual), not a separate auth type. Add the Register an OAuth provider section from #4922 covering both grants, correct UI labels against smith-frontend, scope the self-hosted flag note to v0.17, and rename Headers to Static Headers to match the form.
Collaborator
|
Thanks Rafid S (@rx5ad)! This content is now folded into #6733, which adds the client credentials grant to the same section. I'm closing this PR to avoid a conflict on the same lines. I dropped one line, "Leave the secret empty for public clients": the provider form has no public-client toggle, so the secret is always required. |
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.
What
Adds a Register an OAuth provider section to the Fleet Remote MCP servers page and clarifies the two OAuth 2.1 auth types.
The page told users that OAuth 2.1 (Manual) needs a client ID/secret and a PKCE-enabled provider, but never said where to register that provider or what it requires. This fills that gap:
https://<your-langsmith-host>/host-oauth-callback/<provider-id>), and the PKCE requirement for the provider to be selectable.Accuracy
Every detail is cross-checked against the product code (
CreateOAuthProviderModal,CreateMcpServerModal's PKCE filter, thesettings/oauth-providersroute, and the host-backend callback resolver) — nothing invented.Scope / follow-ups
Intentionally left out (would need confirmation, not documenting speculatively): token refresh/expiry lifecycle for the OAuth paths, and manual-OAuth failure/troubleshooting symptoms.