Question
Virtusa Corportaion
US
Last activity: 14 Sep 2016 10:01 EDT
PegaCLOUD upgrade from 7.1 to 7.2 creates functional issues for SMA, Agents, and SSO via SAMLAuth
The three issues needing assistance asap:
* Authentication fails on External Assignments - users just see a login screen; 'silent' PRRuntime error occurs
* Authentication fails on SSO via SAMLAuth Authentication Service rule; user sees generic 'fail' message with a reference to an unauthenticated requestor; tracer shows compile error in getArtifactIds method
* SMA URL does not work (https://qg-dev.pegacloud.io/prsysmgmt); Agents appear to be inactive as well; error message mentions 'distributed executor' so .do objects appear to be at fault
I have not found any articles related to these issues. See attachments.
Accepted Solution
Virtusa Corportaion
US
Resolutions:
* Authentication fails on External Assignments - users just see a login screen; 'silent' PRRuntime error occurs
Our configuration of the DWA link included query parameters (additional references in the URL). This was an exploit of a bug and should never have worked. For our purposes, we replaced the standard DWA link with a REST URL.
* Authentication fails on SSO via SAMLAuth Authentication Service rule; user sees generic 'fail' message with a reference to an unauthenticated requestor; tracer shows compile error in getArtifactIds method
Our version of the rule called in the Authentication service was out of date.
* SMA URL does not work (https://qg-dev.pegacloud.io/prsysmgmt); Agents appear to be inactive as well; error message mentions 'distributed executor' so .do objects appear to be at fault
Appears to have been combination of issues: TLS settings of the browser; bookmarks without port numbers; new node assignment for dev environment, so existing agent rules did not activate (the rules were not enabled, only the data instances were).
PEG
PL
How the upgrade has been performed?
Have you done the clean restart of the system?
If SMA is available, clear all the cache from in memory and db.
From below error, it suggests that this could be cache issue:
Caused by: com.pega.pegarules.pub.generator.FirstUseAssemblerException: Failed to compile generated Java com.pegarules.generated.activity.ra_action_pysamlwebssoauthenticationactivity_a60e119c83ca80fec4e2febeff169495: ---------- 1. ERROR in /com/pegarules/generated/activity/ra_action_pysamlwebssoauthenticationactivity_a60e119c83ca80fec4e2febeff169495.java (at line 1058) String artifactId = samlutils.generateArtifactId(authnRequest, myStepPage); ^^^^^^^^^^^^^^^^^^ The method generateArtifactId(ClipboardPage) in the type SAMLUtils is not applicable for the arguments (AuthnRequest, ClipboardPage) ---------- 1 problem (1 error) Compile failed.
Also, you could try to delete the below file from the temp directory :
ra_action_pysamlwebssoauthenticationactivity_a60e119c83ca80fec4e2febeff169495
Pegasystems Inc.
US
I think you already have separate questions posted for your issues (which is the right thing to do). For example, SAML issue is tracked here: https://collaborate.pega.com/discussion/case-stages-doesnt-have-sequential-flow and it has already been answered there.
Accepted Solution
Virtusa Corportaion
US
Resolutions:
* Authentication fails on External Assignments - users just see a login screen; 'silent' PRRuntime error occurs
Our configuration of the DWA link included query parameters (additional references in the URL). This was an exploit of a bug and should never have worked. For our purposes, we replaced the standard DWA link with a REST URL.
* Authentication fails on SSO via SAMLAuth Authentication Service rule; user sees generic 'fail' message with a reference to an unauthenticated requestor; tracer shows compile error in getArtifactIds method
Our version of the rule called in the Authentication service was out of date.
* SMA URL does not work (https://qg-dev.pegacloud.io/prsysmgmt); Agents appear to be inactive as well; error message mentions 'distributed executor' so .do objects appear to be at fault
Appears to have been combination of issues: TLS settings of the browser; bookmarks without port numbers; new node assignment for dev environment, so existing agent rules did not activate (the rules were not enabled, only the data instances were).