diff --git a/docs.json b/docs.json index c511e72..8e4d2ce 100644 --- a/docs.json +++ b/docs.json @@ -81,6 +81,7 @@ { "group": "Paid Features", "pages": [ + "paid/sso-authentication", "paid/organization-template-catalog" ] }, diff --git a/images/paid/sso-sign-in.png b/images/paid/sso-sign-in.png new file mode 100644 index 0000000..60578bc Binary files /dev/null and b/images/paid/sso-sign-in.png differ diff --git a/paid/sso-authentication.mdx b/paid/sso-authentication.mdx new file mode 100644 index 0000000..0b05602 --- /dev/null +++ b/paid/sso-authentication.mdx @@ -0,0 +1,29 @@ +--- +title: 'SSO Authentication' +description: "How to enable SSO Authentication in your environment" +icon: 'grid' +--- + +import { NarrowImage } from '/snippets/narrow-image.jsx' + +Most OpenOps features are available in the Community edition, but some are exclusive to the [paid editions](https://www.openops.com/pricing/). + +One such feature, available only in the Enterprise edition, is the **sso authentication**. + +Community and Professional editions include a basic authentication system. The Enterprise edition lets you integrate OpenOps platform with your identity provider using SAML or OIDC. + +SSO Sign-in page + +In larger organizations, this enables centralized identity and access management, allowing IT and security teams to enforce authentication policies, manage user access through existing identity providers, and streamline onboarding and offboarding. + +## Enable SSO for your environment + +OpenOps supports Single Sign-On (SSO) through two authentication methods: +- **SAML** +- **OIDC (OpenID Connect)** + +To learn more or to enable SSO for your environment, please contact your OpenOps account manager. \ No newline at end of file