Support Article
SSO SAML 2.0 Connectivity
SA-1638
Summary
Issues were experienced in achieving connectivity using SAML 2.0 in Pega 7.1.6 for an SSO solution.
The SME made the following summary of the issue:
"Ping Identity is imposing a constraint on the format of the Request ID that it receives. It fails if it does not start with a letter or underscore. This ID is a random UUID generated by PRPC code. It can start with a letter/digit at random.
Below is the error Ping Identity is throwing on their end –
</samlp:StatusMessage><samlp:StatusDetail><Cause>com.pingidentity.common.util.xml.InvalidXmlException: Invalid XML - errors: [error: String: '0bad9553-4fd3-4099-ad32-f1e99033f6ef' does not match pattern for xs:ID]</Cause></samlp:StatusDetail></samlp:Status>
This scenario is very IDP specific and is not a bug in PRPC."
This was discussed with Product Management, who elected to pursue a PRPC product change to supprt the use case requirement.
Error Messages
System Error - Sorry, an unexpected error condition has occurred. Please contact your System Administtrator for assistance and provide the following reference number to help locate additional information about this problem in the system log files.
Error Reference: xzbyoo
(Pingidenity)
Steps to Reproduce
Be on the customer network
Open a new IE session
Navigate to cloud environment SSO URL and login
Root Cause
The random id which was getting generated was using Java UUID. The ping one expects '_' at the beginning.
Resolution
HFix-10026 resolved the problem.
Published January 31, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.