Skip to content

Conversation

@derrickmehaffy
Copy link
Member

What this does

Completely updates all of the SSO documentation for release with Strapi 5

Todo list

  • Initialize all new provider pages
  • Rewrite main SSO configuration page
  • Refactor Discord Provider
  • Refactor Microsoft Provider
  • Refactor GitHub Provider
  • Refactor Google Provider
  • Refactor Keycloak Provider
  • Refactor Okta Provider
  • Add new Auth0 Provider
  • Add new Generic OIDC Provider TODO in the future
  • Add new Generic SAML Provider TODO in the future
  • Add new Gitlab Provider
@derrickmehaffy derrickmehaffy self-assigned this Jan 17, 2025
@derrickmehaffy derrickmehaffy added internal PRs created by the Strapi core team pr: updated content PRs updating existing documentation content size: large If the PR includes 1+ file(s) with a total of 50+ lines of text or 100+ lines of code labels Jan 17, 2025
@vercel
Copy link

vercel bot commented Jan 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
documentation ❌ Failed (Inspect) Jan 17, 2025 5:59pm
- SSO
---

# Discord provider SSO configuration
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep the original title in files


# Discord provider SSO configuration

The present page explains how to setup the Discord provider for the [Single Sign-On (SSO) feature](/user-docs/features/sso).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep this intro. It includes a link back to the feature page

import SSOMiddlewaresConfig from '/docs/snippets/configuration-sso-middlewares.md'

:::prerequisites
You have read the [How to configure SSO guide](/dev-docs/configurations/guides/configure-sso).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please keep the first prereq. It includes a link back to the general guide 🙏

@pwizla pwizla changed the base branch from v6/main to v6/beta February 4, 2025 11:00
@pwizla
Copy link
Collaborator

pwizla commented Feb 4, 2025

@derrickmehaffy , FYI, I changed the base branch to v6/beta as it includes the latest content.

@pwizla pwizla changed the base branch from v6/beta to next February 14, 2025 13:52
@pwizla
Copy link
Collaborator

pwizla commented Feb 14, 2025

Sorry, @derrickmehaffy, many files architecture changes since you started this PR 😅
But the file architecture should be final, now! 🏁

You might want to rebase on next (⚠️ I force pushed with lease on it) and directly target the next branch for your PR.

Here are the different files:

@pwizla pwizla added this to the v6.0.0 milestone Feb 19, 2025
@pwizla pwizla removed this from the v6.0.0 milestone Mar 26, 2025
@pwizla
Copy link
Collaborator

pwizla commented Aug 13, 2025

Hey @derrickmehaffy ,same question as on the other PR:
I'm cleaning up the PR backlog before my vacation.
Should we close this one?
In any case it would need to be rebased on the current CMS docs file architecture

@pwizla pwizla added the flag: don't merge This PR should not be merged at the moment label Aug 13, 2025
@pwizla
Copy link
Collaborator

pwizla commented Dec 17, 2025

Hi @derrickmehaffy , same as for PR 2362, I will close this one to clean up PRs.

@pwizla pwizla closed this Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

flag: don't merge This PR should not be merged at the moment internal PRs created by the Strapi core team pr: updated content PRs updating existing documentation content size: large If the PR includes 1+ file(s) with a total of 50+ lines of text or 100+ lines of code

2 participants