SR-B78496 · Issue 327358
Refined accessgrouplist checks
Resolved in Pega Version 7.4
Following a system modification that changed the property used to populate the accessgroups list to match that on clipboard (correct value), a previously unseen issue was uncovered where all the division and organization AGs were being added to the list. This has been addressed by updating the code to add the applications on division and organization only when there is no default selected at the operator. If there is some application selected as default at the operator, then the division or organization applications will not be added. If there is nothing selected at operator, then a check for division will be made, and if there is nothing selected at division then organization will be checked.
SR-B81365 · Issue 332518
Enhanced security for IAC gadget
Resolved in Pega Version 7.4
The code for the IAC gadget has been reworked to replace eval functions in order to enhance security.
SR-B81365 · Issue 331996
Enhanced security for IAC gadget
Resolved in Pega Version 7.4
The code for the IAC gadget has been reworked to replace eval functions in order to enhance security.
SR-B82500 · Issue 331560
Enhancement to support external delegated authentication via custom authentication
Resolved in Pega Version 7.4
OAuth 2.0 configuration has been embedded into the HC mobile app to provide an infrastructure for REST services to be authenticated by an external token which has been issued by third party identity provider. When Pega receives a token, it then contacts the identity provider's token introspection and userinfo endpoint to validate the token and subsequently establish an identity. The new authentication activity has been shipped with the name 'pyPerformDelegatedAuthentication' that can be attached to any Authentication service data instance.
SR-B82500 · Issue 332132
Enhancement to support external delegated authentication via custom authentication
Resolved in Pega Version 7.4
OAuth 2.0 configuration has been embedded into the HC mobile app to provide an infrastructure for REST services to be authenticated by an external token which has been issued by third party identity provider. When Pega receives a token, it then contacts the identity provider's token introspection and userinfo endpoint to validate the token and subsequently establish an identity. The new authentication activity has been shipped with the name 'pyPerformDelegatedAuthentication' that can be attached to any Authentication service data instance.
SR-B83952 · Issue 338450
Handling added for URL encoding problem
Resolved in Pega Version 7.4
A button configured with 'onClick > Open URL in window' had the "?" replaced by "?=%26" in the URL. This was traced to a safeURL bug which encodes '&' in the URL when there is no key=value pair in the request params. To compensate for this, a design time configuration has been added to skip encoding if the system encounters custom URLs with no key=value pairs.
SR-B84966 · Issue 338317
Handling added for URL encoding problem
Resolved in Pega Version 7.4
A button configured with 'onClick > Open URL in window' had the "?" replaced by "?=%26" in the URL. This was traced to a safeURL bug which encodes '&' in the URL when there is no key=value pair in the request params. To compensate for this, a design time configuration has been added to skip encoding if the system encounters custom URLs with no key=value pairs.
SR-B85132 · Issue 334749
SAML enhancements added with OperatorContext availability fix
Resolved in Pega Version 7.4
The activity pyEstablishOperatorContext availability was incorrectly marked as final. This has been fixed and is "Available, Extension". In addition, many other enhancements have been added towards the goal of no-code configuration of SAML SSO authentication. SAML SSO is the most widely used authentication in production, but has historically required complex custom code. Please see the release notes for more information about Single Page UI Configuration and Adaptive Design for Authentication Run-time.
SR-B86311 · Issue 336269
Enhanced security by masking requestor-ID
Resolved in Pega Version 7.4
In order to improve session security against potential hijacking of a session, the Pega-RULES cookie will be masked in various locations, such as log files, SMA, tracer, exceptions, etc. by exposing only the first character (as it depicts the type of requestor) and the last four characters.
SR-B86311 · Issue 338968
Enhanced security by masking requestor-ID
Resolved in Pega Version 7.4
In order to improve session security against potential hijacking of a session, the Pega-RULES cookie will be masked in various locations, such as log files, SMA, tracer, exceptions, etc. by exposing only the first character (as it depicts the type of requestor) and the last four characters.