SR-103429 · Issue 136984
Rule-Service-Java authentication in a stateless session re-enabled
Resolved in Pega Version 7.1.7
When exposing Rule-Service-Java through a service package, a proxy jar file is created. If the 'Requires Authentication' option was checked on the service package, the generated java did not contain the required code to pass through the username/password and authentication failed. This method of passing credentials via proxy method parameters was previously withdrawn for the stateless processing mode, but the java code has been reinstated to enable authentication for a stateless session if this method is desired.
SR-117840 · Issue 170516
Autopopulate correctly set/disabled in the CSR portal
Resolved in Pega Version 7.1.7
Switching to some clipboard pages caused a null pointer error in the CSR portal for the operator. This was caused by an autopopulate call being made even when autopopulate was disabled. This has been corrected.
SR-118259 · Issue 173287
LookupList opened to unauthenticated requests
Resolved in Pega Version 7.1.7
When a list lookup was called from an unauthenticated service, it failed due to the lack of required authentication. The activity RULE-CIRCUMSTANCE-DEFINITION LOOKUPLIST has been modified to allow its execution by an unauthenticated requestor.
SR-116445 · Issue 169717
SOAP settings updated to work with IBM JBK 1.7
Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on WebSphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
114971 · Issue 164164
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
114971 · Issue 165871
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
116448 · Issue 166844
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
114971 · Issue 164164
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
114971 · Issue 165871
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.
SR-
116448 · Issue 166844
SOAP settings updated to work with IBM JDK 1.7
Resolved in Pega Version Pega Platform, Resolved in Pega Version 7.1.7
When calling Service SOAP hosted on Websphere 8.5+ and JDK 1.7, the SOAP client was failing with a java.lang.VerifyError. This was traced to a change in the settings necessary for use with IBM JBK 1.7, and the needed properties have been updated.