Configuring application SSO in Forcepoint ONE SSE

Configure single sign-on for cloud applications and then configure policies to audit and control access to these protected cloud applications.

Forcepoint ONE SSE integrates at the authentication step and thus requires SSO to be setup in your application before it can determine managed or unmanaged devices and apply policies.

Select and deploy the SSO method appropriate for your application and organization. This may be SAML relay with a third party IdP, SAML relay with Forcepoint’s built-in IdP, or SAML ACS proxy with a third party IdP.

• Microsoft 365: Deploying Forcepoint ONE SSE as a SAML IdP
  Note: Alternatively, if you want to provide agentless secure access to Microsoft 365 applications through the Forcepoint ONE SSE reverse proxy while using Azure AD as IdP, then follow the steps mentioned under Azure AD IdP: Configuring Reverse Proxy for Microsoft 365.
• Sharepoint: Configuring SSO with Forcepoint ONE SSE
• Google Workspace: Deploying Forcepoint ONE SSE as a SAML IdP
• DropBox: Deploying Forcepoint ONE SSE as a SAML IdP
• Box: Deploying Forcepoint ONE SSE as a SAML IdP
• Amazon Web Services: Deploying Forcepoint ONE SSE as a SAML IdP
• Slack: Deploying Forcepoint ONE SSE as a SAML IdP
• Salesforce: Deploying Forcepoint ONE SSE as a SAML IdP
• Service Now: Deploying Forcepoint ONE SSE as a SAML IdP
• Atlassian (Confluence and Jira): Deploying Forcepoint ONE SSE as a SAML IdP
• GitHub: Deploying Forcepoint ONE SSE as a SAML IdP
• Any Managed Application: Deploying Forcepoint ONE SSE as a SAML IdP