INC-188128 · Issue 671828
Refresh assignment checks updated
Resolved in Pega Version 8.6.3
Additional privilege checks have been added to refresh assignment.
INC-188162 · Issue 673508
RSA-PSS signature support added for for SAML SSO
Resolved in Pega Version 8.6.3
The XML security jars have been updated to incorporate RSA-PSS signature algorithm support.
INC-188889 · Issue 675581
New application wizard security updated
Resolved in Pega Version 8.6.3
Security around displaying and running the new application wizard has been enhanced.
INC-189989 · Issue 675573
Refresh assignment checks updated
Resolved in Pega Version 8.6.3
Additional privilege checks have been added to refresh assignment.
INC-190384 · Issue 676574
URL validation updated to handle custom token endpoints
Resolved in Pega Version 8.6.3
While saving an authentication profile with OAuth details, validation was failing for a valid URL given in the access token endpoint and revoke token endpoint fields. This was traced to the use of the Apache URL validator, which considered some domains to be invalid. To resolve this, the urlvalidator constructor has been updated to include a custom RegexValidator for access token and refresh token URLs.
INC-193561 · Issue 680428
Client secret made optional for JWT Bearer Grant type
Resolved in Pega Version 8.6.3
After update, trying to connect a REST API using OpenAM as the provider for OAuth and using JWT Bearer as Grant type was resulting in an error indicating the request was not reaching the destination. This was traced to the client secret being designated a mandatory field when it should be optional in this case as the required key store was already configured with a JWT token profile. To resolve this, an update has been made which will make the client secret optional when the authentication scheme is JWT Bearer. In addition, the blank value caused a null pointer error when the client secret was not passed. This has been handled with a check.
INC-194865 · Issue 695621
Corrected report definition save-as-image option
Resolved in Pega Version 8.6.3
Attempting to save a report definition as an image resulted in an access denied error stating "Browser fingerprint validation failed : A request was received with an invalid or missing browser fingerprint. The request was denied", and the user session was closed. The security SECU0017 alert is generated when a request is sent to a Pega application and the browser fingerprint is either missing or does not match the expected value. The system tries to check the type of request for every requestor ID and fetch the CSRF token, but in this case it was not matching with the token present on the requestor thread. This has been resolved by adding scripts to send the hidden input value needed.
INC-196414 · Issue 684239
OAuth token refreshed when revoked on source
Resolved in Pega Version 8.6.3
When an OAuth token was used to authorize the APIs in the system, revoking the token at the source, i.e. from the Service side, did not automatically refresh the token and a logoff/logon was required before a fresh token was generated. This has been resolved by adding an update to explicitly purge revoked tokens.
INC-196431 · Issue 684887
Refresh assignment checks updated
Resolved in Pega Version 8.6.3
Additional privilege checks have been added to refresh assignment.
INC-196839 · Issue 695282
Removed duplicate clipboard page creation
Resolved in Pega Version 8.6.3
An out of memory exception occurred due to the pyInstanceInfoForUpdate clipboard page having 6.5M Embed-InstanceInfo entries. This was traced to the ClientUpdateRequestHandler.getInstanceInfoPage method continuously appending to the ClipboardProperty instanceInfoPage. This has been resolved by removing the extra creation of instance pages within the loop.