Verify the following prerequisites for SSO configuration:
SSO configuration for PingIntelligence Dashboard involves configuring both Dashboard and PingOne.
  1. Create an OIDC (OpenID Connect) web application in PingOne to setup SSO to PingIntelligence Dashboard . To configure the OIDC application, complete the steps explained in Configuring an OIDC Application in PingOne for PingIntelligence Dashboard.
  2. Set the value of pi.webgui.server.authentication-mode to sso in <pi_install_dir>/pingidentity/webgui/config/ file.
    ### Authentication mode
    # valid values: native, sso
    Note: PingIntelligence for APIs Dashboard provides two methods for user authentication: native or SSO. SSO authentication should be used only for production deployments. Use native authentication for PoC deployments.
  3. Configure the <pi_install_dir>/pingidentity/webgui/ file to complete the PingIntelligence Dashboard's SSO authentication. For more information, see Configuring Dashboard for PingOne.
  4. Obfuscate keys added in SSO properties using the following commands.
    # cd <pi_install_dir>/pingidentity/webgui
    # ./bin/ obfuscate_keys
  5. Restart the PingIntelligence Dashboard after configuring SSO in PingOne and PingIntelligence Dashboard. For more information, see Start and stop Dashboard.
  6. When the PingIntelligence Dashboard is started successfully, access it using https://<pi_install_host>:8030. The Dashboard will start SSO Authentication, and a new session will get created for the logged-in users.
If the SSO authentication fails for any reason, PingIntelligence Dashboard shows the following error message.
Screenshot for PingIntelligence Dashboard SSO error

Note: Every PingIntelligence Dashboard SSO authentication event is attached with a unique ID, which is logged in <pi_install_dir>/pingidentity/webgui/logs/admin/sso.log. You can filter sso-event-ref = <unique ID> in the <pi_install_dir>/pingidentity/webgui/logs/admin/sso.log file to find the reason for SSO failure.