Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

SSO login to production is not happening from OKTA

SA-33598

Summary



User have updated from Pega 7.2 to 7.2.1.

They are getting below exceptions.


Error Messages


2017-02-11 20:47:23,239 [ttp-apr-8080-exec-12] [ STANDARD] [ ] [ CECFW:01.03.01] ( internal.util.PRSAMLv2Utils) ERROR jeldwn-prod1.pegacloud.io|66.190.230.218 - Caught Exception while processing SAML2 Authentication response
org.opensaml.xml.parse.XMLParserException: Invalid XML
at org.opensaml.xml.parse.BasicParserPool.parse(BasicParserPool.java:221)
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.unmarshallMessage(PRSAMLv2Utils.java:448)
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.getSAMLObject(PRSAMLv2Utils.java:545)
at com.pega.pegarules.integration.engine.internal.util.PRSAMLv2Utils.processAuthenticationResponse(PRSAMLv2Utils.java:500)
at com.pegarules.generated.activity.ra_action_pysamlwebssoauthenticationactivity_9d5638695a06f103bb9c1d6a6bfb724e.step16_circum0(ra_action_pysamlwebssoauthenticationactivity_9d5638695a06f103bb9c1d6a6bfb724e.java:1723)
at com.pegarules.generated.activity.ra_action_pysamlwebssoauthenticationactivity_9d5638695a06f103bb9c1d6a6bfb724e.perform(ra_action_pysamlwebssoauthenticationactivity_9d5638695a06f103bb9c1d6a6bfb724e.java:367)

Caused by: org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 348; Element type "saml2p:Response" must be followed by either attribute specifications, ">" or "/>".
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:198)
at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.fatalError(ErrorHandlerWrapper.java:177)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:400)
at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:327)
at com.sun.org.apache.xerces.internal.impl.XMLScanner.reportFatalError(XMLScanner.java:1465)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.seekCloseOfStartTag(XMLDocumentFragmentScannerImpl.java:1390)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:265)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl$NSContentDriver.scanRootElementHook(XMLNSDocumentScannerImpl.java:619)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:3129)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(XMLDocumentScannerImpl.java:880)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:118)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:504)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:243)
at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:338)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
at org.opensaml.xml.parse.BasicParserPool$DocumentBuilderProxy.parse(BasicParserPool.java:696)
at org.opensaml.xml.parse.BasicParserPool.parse(BasicParserPool.java:218)
... 62 more


Steps to Reproduce



Not Applicable


Root Cause



An issue in the custom application code or rules, user upgraded the system to Pega 7.2.1 without proper Hfix.

Resolution



Revert the upgrade to Pega 7.2.0 to stable the system in production environment.

Additionally apply HFix-32265 to address the reported issue.

Published March 16, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us