INC-229319 · Issue 739145
Service registry queries optimized
Resolved in Pega Version 8.8
Full table scans were being performed by queries running against pr_sys_serviceregistry_kvs and pr_sys_serviceregistry table. This has been resolved by optimizing service registry queries to avoid full table scans.
SR-D83605 · Issue 545587
Resolved cookie issue for Service call headers
Resolved in Pega Version 8.3.3
After upgrade, a difference in how cookies were passed in headers in Service calls resulted in failing to capture the HTTP cookie header necessary to support frontend digital signing. This has been resolved by modifying the code positioning and conditionalizing the resolved value check.
INC-219161 · Issue 724834
OAuth token handling updated for integrated service
Resolved in Pega Version 8.8
After implementing Webex integrations (appointments & spaces), authorization issues were seen with the error "Cannot retrieve tokens for [email protected] as the logged session is with [email protected]". This was an issue relating to operator validation from requestor page, and has been resolved.
INC-157196 · Issue 629298
Deprecated service package features now require authentication
Resolved in Pega Version 8.5.3
Authentication has been added to deprecated features of the standard service package to improve security. If issues are encountered during product migration, please use the Deployment Manager.
INC-150610 · Issue 627428
Argument number exception handled for SERVICES-PAL log configuration
Resolved in Pega Version 8.5.3
An issue with being unable to configure the SERVICES-PAL log file has been resolved by adding handling for an unlogged "wrong number of arguments" exception.
INC-211349 · Issue 709607
Service API called directly in CDH simulation
Resolved in Pega Version 8.8
Running a simulation from the Customer Decision Hub with strategy and dataflow that used customer data resulted in with either a failed run or blank explain detail reports. Investigation showed synchronization was not triggered due to the pxVBDAvailable call returning false, and this has been resolved by directly calling the service API without additional checks.
INC-227812 · Issue 733965
Service SOAP outflow response supports RSA_SHA256 & RSA_SHA384
Resolved in Pega Version 8.8
When service SOAP was configured in Pega WS-Security Profile with with outflow as signature and the signature method selected as RSA_SHA256, the response from service SOAP was still RSA_SHA_1 and the digest method was SHA_256. This has been resolved by updating WS-Security Profile to support RSA_SHA256 & RSA_SHA384 in service SOAP outflow response.
INC-157194 · Issue 620153
CheckRevisionDeployment requires authentication
Resolved in Pega Version 8.5.3
Authentication has been added to the CheckRevisionDeployment service package.
INC-234134 · Issue 742477
Connection list API call will be skipped when not configured
Resolved in Pega Version 8.8
An exception was appearing as part of Robotic Desktop Automation (RDA) flow whenever message service host was not configured. This has been resolved by skipping the connection list API call when the message service host is not configured. A specific Pega log and console log messages have also been added.
INC-155813 · Issue 629506
SAML SSO redirects to correct URL when application and authentication aliases match
Resolved in Pega Version 8.5.3
Whenever there was a match in the authentication service alias and the application alias, the application alias was replaced with empty after logoff instead of making the authentication service alias empty. For example, given an authentication service with the alias XYZ ("login with XYZ" alias option) and an application name XYZMyOps, the application alias was being changed from XYZMyOps to appMyOps after logoff. As a result, a blue screen error resulted when clicking on button "login with XYZ" again because it redirected to appMyOps, which didn't exist. This has been resolved by removing authservicealias and modifying AuthServiceAliasHelper.adjustPathIfAuthServiceAliasPresent() to change the method for calculating the pathinfo to string tokenizing