Question

3
Replies
726
Views
 Joel Wells (JRWells_Virtusa)
Virtusa Corportaion
Senior Architect
Virtusa Corportaion
US
JRWells_Virtusa Member since 2005 8 posts
Virtusa Corportaion
Posted: August 24, 2016
Last activity: September 21, 2016
Posted: 24 Aug 2016 13:53 EDT
Last activity: 21 Sep 2016 6:25 EDT
Closed
Solved

Authentication: SSO via SAML failing after upgrade to 7.2.1

After upgrading out PegaCLOUD instance to 7.2.1, we get the following error when logging in using SSO via SAMLAuth Authentication rule:

The method generateArtifactId(ClipboardPage) in the type SAMLUtils is not applicable for the arguments (AuthnRequest, ClipboardPage)
----------
1 problem (1 error)
Compile failed.

 

The method is called in Activity rule pySAMLWebSSOAuthenticationActivity, step 5.

Full tracer results attached.

***Updated by Moderator: Vidyaranjan. Removed user added  Ask the Expert tag. Apologies for confusion, shouldn't have been an end-user option***

System Administration Upgrades Security Support Case Exists
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 24 Aug 2016 15:59 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Software Solutions Engineering
Pegasystems Inc.
US

Can you double check if your pySAMLWebSSOAuthenticationActivity is from 7.2.1 OOTB rule? The OOTB call is


                            String artifactId = samlutils

                                    .generateArtifactId(myStepPage);


You can see only taking one argument.
Posted: 4 years ago
Posted: 24 Aug 2016 16:17 EDT
Chris Koyl (ChrisKoyl)
PEGA
Client Support Engineer Senior Fellow
Pegasystems Inc.
US

Just to add to the response from Kevin.


From the tracer it's not even compiling so pretty sure it's a copy from previous release.  For example in PRPC 7.1.8 it's:


String artifactId = samlutils.generateArtifactId(authnRequest, myStepPage);


Now it's changed in 7.2:


String artifactId = samlutils.generateArtifactId(myStepPage);


The copy of the activity would be part of a ruleset that is defined in the AccessGroup used in the Data-Admin-Requestor [SystemName] Browser instance. This is known as the unauthenticated AccessGroup.


Note:


There is a lot of Java in this activity to handle SAML and it's going to change between releases. See if it makes sense to move your customization to the pyEstablishOperatorContext activty. This is called from pySAMLWebSSOAuthenticationActivity.