Docs
Search
Search
Help & Feedback
Get Started
Functionality
Learning
Extension
Dev Tooling
APIs
Releases
SSO Configuration and Management Guides
Collection of articles covering SSO and identity configuration.
Azure AD & Microsoft Entra ID OIDC Configuration: Unified Guide
How-to Guide
Adding the application to PingOne
Registering application with Microsoft
Getting the client ID and client secret for the application
Setting up API permissions
Adding the identity provider in PingOne
Adding the Redirect URI to the Microsoft portal
Do not forget
Azure AD & Microsoft Entra ID SAML Configuration: Unified Guide
How-to Guide
It is possible to use the generic SAML configuration to add an external identity provider that follows the SAML standard.
Steps to configure an external identity provider via SAML configuration
Azure Single Logout configuration
How-to Guide
The article offers detailed instructions for setting up Single Logout (SLO) for Azure AD, serving as an external identity provider.
Users can establish a robust authentication system by following the precise steps outlined, enhancing security and efficiency.
Configure Okta connection via SAML
How-to Guide
Register application with Okta
Add the identity provider in PingOne
Add Metadata URL
Continue IDP Configuration
Do not forget
Configure session timeout for SSO users with external IDPs (Okta)
How-to Guide
Configure Fluent OMS session timeout for SSO users with external IDPs (Okta)
Configure session timeout for SSO users without external IDPs
How-to Guide
Session timeout for Fluent OMS can be configured for SSO users without external IDPs via Ping Identity.
In order to configure the timeout, you would need to configure Access token time to live and the authentication policy on Ping Identity.
Fluent OMS session timeout configuration for SSO users with Azure as an external IDP
How-to Guide
The article offers a step-by-step configuration for setting up Fluent OMS session timeout specifically tailored for Single Sign-On (SSO) users.
It focuses on configuring session timeout within Fluent OMS while utilizing Azure as the external Identity Provider (IDP).
Renew SSO (SAML External IDP) Certificate in Ping
How-to Guide
This guide explains how to renew Fluent SSO in Ping using a new certificate from your external SAML IDP
The activity is performed by the Ping admin user set up by Fluent
A new certificate from your external IDP provider is required
The update takes only a few minutes to complete
No downtime is required
SSO - Multi-Factor Authentication (MFA) Configuration
How-to Guide
In order to enable MFA, you need to log into pingOne to make sure that MFA is enabled for Fluent App and for the logged user.
You would then need to log in the system via Fluent’s self service link.
Once this has been completed, a new authentication method needs to be added on Ping Identity.
SSO Configuration for Vendor Access
How-to Guide
Enables single sign-on access to Fluent OMS for multiple organizations.
PingOne automatically routes users to the correct IdP by email domain.
Requires connecting all relevant IdPs (e.g., Google Workspace, Azure AD).
Uses an Authentication Policy in PingOne to define domain-based rules.
Each user is linked to an Authoritative IdP that manages authentication.
Provides a unified, secure, and streamlined login experience for all users.
SSO Enablement Process
How-to Guide
In order to configure the SSO, you would need to first sign the DPA, define the number of required SSO users, and raise a support ticket.
Second step is to configure your company IDP in Ping Identity.
Third step is to test to test to make sure that the user can log in.
SSO: Configure Google Workspace connection via SAML
How-to Guide
This guide covers setting up an SSO connection between PingOne and Google Workspace using SAML.
Ensure you have admin access in PingOne and a Google Workspace account with an active subscription.
You need to register the application in Google Workspace to configure it as an external identity provider.
SSO: Configure JumpCloud connection via SAML
How-to Guide
It is possible to use the generic SAML configuration to add an external identity provider that follows the SAML standard
This page provides a guide on how to configure an external identity provider via SAML configuration.
Switch the Fluent App to Opaque Refresh Tokens in PingOne
How-to Guide
Removes the PingOne warning "Update this application to use opaque refresh tokens" from the Fluent App in your SSO environment
Required before March 1, 2027, when PingOne stops supporting JSON Web Token (JWT) refresh tokens
Changes only the refresh token format. Sign-in to Fluent Web Apps is not affected
Requires admin access to your PingOne SSO environment