DaaS / Products / Publish then SSO-Gate Documentation Portal

Publish then SSO-Gate Documentation Portal

A developer first publishes a GitBook documentation site with custom domain and GitHub sync, then embeds it into their customer-facing portal and integrates IDaaS SSO so only authenticated enterprise users can access private documentation sections.

Products involved

Scenario

A developer first publishes a GitBook documentation site with custom domain and GitHub sync, then embeds it into their customer-facing portal and integrates IDaaS SSO so only authenticated enterprise users can access private documentation sections.

How the products combine

  1. gitbook+idaas · authenticated-embedded-documentation-portal-a64abf — Authenticated Embedded Documentation Portal

    2. See _combos/authenticated-embedded-documentation-portal-a64abf.

  2. alinux+oss+rds+alinux+oss+rds+ecs+oss+terraform+ecs+rds+terraform+alinux+rds+ecs+oss+terraform+alinux+rds+es+opensearch+oss+es+rds+es+supabase+ecs+oss+terraform+es+idaas+es+opensearch+oss+es+rds+es+supabase+es+rds+oceanbase+pai+rds+rds+es+opensearch+oss+es+rds+es+supabase+es+opensearch+oss+es+rds+es+supabase+rds+gitbook+gitbook+idaas · compliant-platform-with-authenticated-docs-2281a1 — Compliant Platform with Authenticated Docs

    3. See _combos/compliant-platform-with-authenticated-docs-2281a1.

  3. gitbook · gitbook-publish-site — GitBook Publish a Documentation Site

    4. See gitbook/gitbook-publish-site.

  4. gitbook+idaas · sso-protected-embedded-documentation-646b86 — SSO-Protected Embedded Documentation

    5. See _combos/sso-protected-embedded-documentation-646b86.

Typical questions

FAQ

Q: How can I publish a GitBook documentation site and protect it with SSO? A: You can achieve this by publishing a GitBook documentation site with a custom domain and GitHub sync, embedding it into your customer-facing portal, and integrating IDaaS SSO to restrict access to authenticated enterprise users. This configuration combines GitBook publishing with IDaaS authentication to create an SSO-protected embedded documentation portal. The setup ensures that only verified enterprise users can view private documentation sections after logging in.