Repository navigation
Improve authentication overview page for discoverability - #7721
Open
fern-api[bot] wants to merge 1 commit into
Open
fern-api[bot] wants to merge 1 commit into
fern-api[bot] wants to merge 1 commit into
Conversation
fern-api
Bot
requested review from
jkonrath-postman and
nerminamiller-postman
as code owners
November 2, 2026 16:32
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
| Yes. Fern's SSO works with any SAML 2.0 or OIDC provider, including Microsoft Entra ID (formerly Azure AD). [Contact Fern](https://buildwithfern.com/book-demo) to set it up. | ||
| </Accordion> | ||
| <Accordion title="Can I integrate SSO with third-party service users (not just internal employees)?"> | ||
| Yes. SSO is not limited to internal teams. You can gate docs for any audience — partners, customers, or external developers — as long as they authenticate through your identity provider. Combine SSO with [RBAC](/learn/docs/authentication/features/rbac) to show different content to different user groups. |
Contributor
There was a problem hiding this comment.
🚫 [vale] <Microsoft.Contractions> reported by reviewdog 🐶
Use 'isn't' instead of 'is not'.
Suggested change
| Yes. SSO is not limited to internal teams. You can gate docs for any audience — partners, customers, or external developers — as long as they authenticate through your identity provider. Combine SSO with [RBAC](/learn/docs/authentication/features/rbac) to show different content to different user groups. | |
| Yes. SSO isn't limited to internal teams. You can gate docs for any audience — partners, customers, or external developers — as long as they authenticate through your identity provider. Combine SSO with [RBAC](/learn/docs/authentication/features/rbac) to show different content to different user groups. |
| Yes. SSO is not limited to internal teams. You can gate docs for any audience — partners, customers, or external developers — as long as they authenticate through your identity provider. Combine SSO with [RBAC](/learn/docs/authentication/features/rbac) to show different content to different user groups. | ||
| </Accordion> | ||
| <Accordion title="Which authentication method supports API key injection?"> | ||
| JWT and OAuth both support [API key injection](/learn/docs/authentication/features/api-key-injection), which pre-fills a user's API key in the API Explorer after they log in. SSO and password protection do not support API key injection. |
Contributor
There was a problem hiding this comment.
🚫 [vale] <Microsoft.Contractions> reported by reviewdog 🐶
Use 'don't' instead of 'do not'.
Suggested change
| JWT and OAuth both support [API key injection](/learn/docs/authentication/features/api-key-injection), which pre-fills a user's API key in the API Explorer after they log in. SSO and password protection do not support API key injection. | |
| JWT and OAuth both support [API key injection](/learn/docs/authentication/features/api-key-injection), which pre-fills a user's API key in the API Explorer after they log in. SSO and password protection don't support API key injection. |
Contributor
|
🌿 Preview your docs: https://fern-preview-2026-11-02-fern-ai-2fbdc2-289a1c4f.docs.buildwithfern.com/learn Here are the markdown pages you've updated: |
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.
Updated
fern/products/docs/pages/authentication/overview.mdxwith four changes: (1) changed the pagetitlefrontmatter to "Authentication overview" and updateddescriptionto name supported providers and auth methods for better search discoverability; (2) added an introductory paragraph before the CardGroup that names all supported SSO providers and links to RBAC; (3) updated the SSO bullet in "Which option should I use?" to list all supported providers inline and removed the old "(Okta, Google Workspace, etc.)" parenthetical; (4) added a "## Common questions" section at the bottom with four<Accordion>items covering Entra ID SSO support, third-party service user SSO, API key injection method support, and plan availability.