INC-185482 · Issue 670107
Certificate expiration notice toggle correctly updates
Resolved in Pega Version 8.7
Clicking the Configure notifications for expiring certificates toggle to switch it off was still showing the toggle as on after refresh. This has been corrected
INC-185514 · Issue 668029
Certificate expiration notice toggle correctly updates
Resolved in Pega Version 8.7
Clicking the Configure notifications for expiring certificates toggle to switch it off was still showing the toggle as on after refresh. This has been corrected
INC-186395 · Issue 677205
Updating handling for for Pega-supplied operators with MFA
Resolved in Pega Version 8.7
When a site is blocking prweb and using prweb/PRAuth for login with MFA enabled, admin user id logins failed and MFA showed the error screen for Pega-supplied users. This was due to MFA verification not being configured for Pega-supplied operators, and has been resolved by adding an Adminstrator condition to skip MFA for for Pega-supplied operators.
INC-186512 · Issue 669328
Password security enhanced
Resolved in Pega Version 8.7
Security and authentication have been enhanced for password handling.
INC-188128 · Issue 671829
Refresh assignment checks updated
Resolved in Pega Version 8.7
Additional privilege checks have been added to refresh assignment.
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-188889 · Issue 675580
New application wizard security updated
Resolved in Pega Version 8.7
Security around displaying and running the new application wizard has been enhanced.
INC-189989 · Issue 675572
Refresh assignment checks updated
Resolved in Pega Version 8.7
Additional privilege checks have been added to refresh assignment.
INC-190384 · Issue 676573
URL validation updated to handle custom token endpoints
Resolved in Pega Version 8.7
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 680427
Client secret made optional for JWT Bearer Grant type
Resolved in Pega Version 8.7
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.