Skip to main content

Resolved Issues

View the resolved issues for a specific Platform release.

Go to download resolved issues by patch release.

Browse release notes for a selected Pega Version.

NOTE: Enter just the Case ID number (SR or INC) in order to find the associated Support Request.

Please note: beginning with the Pega Platform 8.7.4 Patch, the Resolved Issues have moved to the Support Center.

INC-157095 · Issue 638806

Enhancement added for tenant-level authentication

Resolved in Pega Version 8.6.1

In a multi-tenant PDC with a few tenants that utilize their own custom SSO, a pre-authentication activity inside a tenant that should block community access was also affecting tenants that did not have that pre-auth activity set. This was a missed use case and has been resolved by adding a tenantId hash in SchemePRAuth.makeUniqueSchemeName() to create the authServiceName.

INC-162434 · Issue 640050

LookUpList correctly executes during SSO login with model operator

Resolved in Pega Version 8.6.1

After configuring SSO to create operators on fly using a model operator, a new user logging in for the very first time had their operator ID created using the model operator, but after update new users logging in to the system received the error "Only authenticated client may start this activity: RULE-OBJ-ACTIVITY @BASECLASS LOOKUPLIST". This was due to the methods used for additional security on the activity @baseclass LookUpList which allows it to only be run by authenticated users, and has been resolved

INC-163201 · Issue 646912

BrowserFingerprint updated

Resolved in Pega Version 8.6.1

Security improvements have been added to the browser fingerprint process.

INC-168837 · Issue 646974

CSRF token updated for use with OKTA login

Resolved in Pega Version 8.6.1

An issue seen while connecting via OKTA has been resolved by updating the CSRF token validation for use with IDP initiated SSO login.

INC-169186 · Issue 655538

Disconnect button availability extended

Resolved in Pega Version 8.6.1

A case was not refreshing when the disconnect button was selected while using the standard section for authorization grant type authentication. This was traced to a query executed to find a div with attribute pzInsHandle, but that attribute was not applicable in the user portal. To support this use, the query has been extended to be applicable for user portal (attribute data-ui-meta) and Dev Studio landing page.

INC-169310 · Issue 649712

Cache check added for SQL queries

Resolved in Pega Version 8.6.1

When performing load testing, a high number of gets were seen for some SQL Queries. In order to improve performance, a check has been added in GlobalTrustStoreCacheImpl.java to assess whether the cache has been initialized or not.

INC-170423 · Issue 648983

Added catch for SAML WebSSO duplicate key exception

Resolved in Pega Version 8.6.1

After logging in from SSO, closing the Pega window and opening it again resulted in the error "Unable to process the SAML WebSSO request : Violation of PRIMARY KEY constraint. Cannot insert duplicate key in object." This has been resolved by updating the session index handling and adding a catch for the duplicate key exception.

INC-171875 · Issue 653893

Skip restored for browser request CSRF token

Resolved in Pega Version 8.6.1

Many SECU0008 alerts were seen in the production logs. This was the result of a CSRF token check on requests without pyActivity or pyStream, and has been resolved by restoring a conditional skip of the check as those other browser requests do not contain a CSRF token.

INC-173294 · Issue 650235

Mobile "Forgot Password" supports circumstanced rule

Resolved in Pega Version 8.6.1

An enhancement has been added to support a circumstanced rule for the "Forgot Password" flow on mobile.

INC-175058 · Issue 660934

SSLContext created using protocol from REST connector rule form

Resolved in Pega Version 8.6.1

After upgrading to IBM websphere v9.0.5.6 or higher, API calls Like REST, Connect-HTTP etc were failing to connect to endpoints using TLSv1.2. Investigation showed that although the connector was configured to send TLSv1.2, the ClientHello handshake was triggered for TLSv1.3. Because the SSLContext was created with highest version supported by protocol in the WAS container, this has been resolved by modifying the code to create SSLContext based on the the protocol selected in the REST connector rule form. Additionally, please note that the Connect-HTTP connector has been deprecated and the Connect-REST capabilities in the platform should be used instead.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us