INC-188162 · Issue 673507
RSA-PSS signature support added for for SAML SSO
Resolved in Pega Version 8.7
The XML security jars have been updated to incorporate RSA-PSS signature algorithm support.
INC-160485 · Issue 655297
Trailing "/" added to public links for SSO use
Resolved in Pega Version 8.7
Links generated using pyWorkLinkWithLabel were not working with SSO due to not having a trailing "/" on the URL. This has been corrected by adding code to append the "/" if the public link url doesn't end with it.
SR-B69359 · Issue 337302
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-C11323 · Issue 352191
Tab header value works for SSO
Resolved in Pega Version 8.1
The Tab header value was not updated with the rule name or Work Object ID when SSO authentication was used with sub-domain URLs. This has been fixed.
SR-A14336 · Issue 230881
Resolved NPE when @checkForSubstitute used
Resolved in Pega Version 7.2.1
If an assignment used the "Check Availability" setting and the operator was not available at that time, a NPE was generated in cases where the timezone needed to be parsed to complete the check. To correct this, the system has been modified to support time zones with more than 3 characters, and support was added for the IST timezone.
INC-178148 · Issue 660924
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
INC-188405 · Issue 673063
Handling added for SSO servlet name
Resolved in Pega Version 8.7
After update, logging into an external site was not working correctly due to the SSO URL being appended with "/app/default". This has been resolved by updating the code to handle the servlet name properly.
SR-D29127 · Issue 506863
SAML data pages restored after passivation
Resolved in Pega Version 8.2.4
If login used SAML SSO, resuming the session after passivation resulted in missing or empty data pages when using an SAP integration with Pega Cloud. This was traced to a security change that modified the D_SAMLAssertionDataPage and D_SamlSsoLoginInfo data pages as readonly, causing them to not be passivated under these conditions. To resolve this, the data pages have been made editable so they will be restored as expected. This change also resolves any difficulty with SAML logoff activities in conjunction with SAP and Pega Cloud.
SR-C16944 · Issue 364121
pxObjClass of StepPage retained when using adoptJSONObject
Resolved in Pega Version 8.1
When using the adoptJSONObject method in a REST Service activity, calling adoptJSONObject made the pxObjClass of StepPage null. However, the pxObjClass retained its correct value after calling the adoptJSONObject method if the tracer was running. In this scenario, when JSON was adopted on to a page which had pxObjClass set on it and JSON didn't have pxObjClass within it , the resulting page was becoming classless. This has been fixed by reading pxObjClass from the page and retaining it if it is not empty and if pxObjClass is not present in stream.
SR-A11447 · Issue 243018
Importing an archive no longer fails when using DynaTrace
Resolved in Pega Version 7.2.1
Importing an archive was failing when using the third party program DynaTrace. This was due to passivation during the import process, and the system has been modified to prevent this.