SSO known issues for Clarity - master KB
Article ID: 224662
Updated On:
Products
Clarity PPM On Premise
Clarity PPM SaaS
Issue/Introduction
A list of known issues related to Single Sign on (SSO)
Resolution
Table of Contents
As the list of articles below is not a full list of KBs, if a match for your issue isn’t found below, also search using the Broadcom support search portal. See Known Clarity issues: Tips in using self service.
General
- Unable to connect via SAML SSO - redirected to ErrorURL / Logout URL
- Clarity SAML 2.0 configuration not able to support signed authentication request (DE60227 - Fixed in 15.9.2)
- CSA fields and values needed to populate for SSO to integrate with Clarity
- SSO integration, XOG and Scheduler considerations for Clarity
- SSO changes after refresh on lower environment
- SAML 2.0 integration doesn't work when using SSL offloading on LB in Clarity
Login
- Clarity URL keeps looping when using SAML based authentication
- Blank Page/Login errors "en - Unable to process request..." or "Error 501..." due to corrupted homepage
- Unable to use login page of Clarity after enabling SSO - error "Unable to process request..."
Logout
Modern UX
- Login message not appearing although enabled in MUX - The Login Message will not appear if Clarity 15.9.2 uses SSO. Support for Login Message in an SSO environment has been introduced in 15.9.3
- Navigating to New UX takes you to a login page in custom SSO Configuration - Applicable only if you are CLARITY ON PREMISE and you are using a custom SSO solution by establishing session by invoking SSO.JSP
- SSO not working for Modern UX with SAML
GCP SaaS Specific
- Non-Federated Users log in - How to login in as a non-federated user
- Add a Non-Federated user in Okta - Steps on how to add a non-federated user
- Enabling SSO in Google Cloud Platform for Clarity - Describes the steps that need to be done in order to implement / enable SSO for Clarity SaaS customers in Google Cloud Platform (GCP).
- Clarity SaaS Broadcom Okta URL Update
- SSO Certificate update prerequisites for Clarity SaaS - For any Single Sign On (SSO) enabled environments when the certificate expires for any environment, it needs to be updated at Broadcom as well. This document provides the information that needs to be collected before contacting Broadcom Support for the certificate update.
On Premise
- Track if Clarity has received the header or cookie from SSO (On Premise non SAML)
- SAML configuration with ADFS (Clarity On Premise)
Compatibility/Support
Related Documentation
Additional Information
See also: Clarity frequently reported issues
Feedback
Yes
No
Powered by
