SR-D57038 · Issue 519380
JobScheduler DST handling updated
Resolved in Pega Version 8.2.6
When the locale being used changed out of Daylight Savings Time, scheduled jobs did run at the same local time as before but instead ran an hour earlier than expected. Investigation showed that jobscheduler calculated the next runtime based on the time difference from the cluster reference time and current time in milliseconds, and this offset in milliseconds was added to next run time. Since the cluster was started in DST, the job was running on same time due to the time difference. To resolve this, the system will use a calculation offset and set hours/minutes to nextRunTime object so that calendar lib handles daylight savings.
SR-D58927 · Issue 522290
Added expiration for orphaned tracers
Resolved in Pega Version 8.2.6
After tracing a REST service, the tracer was persisting but not showing in the requestor list from Admin studio. The operator shown in the error did not have access to the system anymore, and other users were not able to trace the service rule. Trying to clear the requestors in all the nodes using API POST /nodes/{nodeID}/pools/requestor/clear also did not resolve the issue. To address this, a distributed rule watch expiration has been added.
SR-D59262 · Issue 523616
Cleanup added for staging directory
Resolved in Pega Version 8.2.6
Temporary files from imports and exports (from DevOps) were filling up the staging area disk space because there was no automatic process for cleaning up these local files. This has been resolved by adding an enhancement that will clear the directory on Engine Startup and any time ParUtils.setStagingDirectory gets called to initialize the staging directory.
SR-D59619 · Issue 520345
Handling updated for comparing timestamps during daylight savings
Resolved in Pega Version 8.2.6
An issue with SOAP authentication that generated the error "wsse:FailedAuthentication The creation time is older than currenttime" was traced to the java library not handling daylight savings time properly. This has been resolved by using joda time to compare time stamps.
SR-D61967 · Issue 528216
Updated key handling for ProcessJWT
Resolved in Pega Version 8.2.6
After configuring an authentication service which used the ProcessJWT activity to validate the token received, the error "Unable to process the Json Web Token " was seen. Analysis showed the error was caused by a duplicate Key Id in JWK Endpoint Response: the system removed keys after processing, and in the case of duplicate keys the system was throwing null pointer exception because the key had already been removed. To resolve this, the system has been updated to not remove the keys from the map as part of this process.
SR-D63668 · Issue 525480
Access Control Policy updated to handle NotEqual with valuelist
Resolved in Pega Version 8.2.6
When editing the Access Control Policy Condition rule in Designer Studio and setting condition to 'is not equal', comparing it to a list generated the error "function not found". The same configuration worked as expected for the 'is equal' condition. This has been resolved by updating policycondition to handle a not equal scenario combined with a valueList property.
SR-D63681 · Issue 527383
Localization added to login page messages
Resolved in Pega Version 8.2.6
Localization has been added to the messages that appear on the login and forgot password screens.
SR-D63727 · Issue 531724
Authorization header base 64 format error recategorized as debug logging
Resolved in Pega Version 8.2.6
Numerous messages were generated indicating that the Authorization Header format was invalid when using the format " : " (Base64 Og==) . As this is the default behavior for a particular class of proxy servers, the error statement has been updated to be logged as a debug statement and will be visible only when that logging is enabled.
SR-D64408 · Issue 530281
Stacktrace will be generated for oLog errors
Resolved in Pega Version 8.2.6
In order to provide improved diagnostics, oLog errors will print stacktraces.
SR-D64608 · Issue 544387
Corrected filedownload extension header issue
Resolved in Pega Version 8.2.6
Filedownload header contained plain non-ascii characters which caused a security violation issue. This has been resolved by removing the filedownload header from the HTTP response when the sendfile API is used with inputstream to download a file.