V8 SP4 Releases
Maintenance window: October 21, 2019 00:01 to 04:00Impacted Cloud services:
Cloud Management Console
Add MFA support for custom identity provider
Engagement
Fix bulk push issue resulting in BatchUpdateException: Failed to save messageentry_status duplicate entry ‘
' for key 'PRIMARY' The frequency of the procedure specifically used for sending ‘scheduled’ pushes for windows, androidjpush, blackberry osTypes has been increased from 5 min to 60 min to reduce database load (as there are no customers actively using these osTypes). Note that ‘immediate’ pushes can still be performed outside of the ‘scheduled’ 60 min frequency.
Identity
Fix browser logout issues in case of Azure AD SAML
Fix login and UI issues in case of OAuth provider
Fix for cors-config does not set console-url in the config to prevent console from getting blocked
Add MFA support for custom identity provider
Integration Server
Fix intermittent socket exceptions occurring on login to DBX when idle for some time
Fix issue introduced in in V8 SP4 FP3 HF6 in which service metadata API calls were failing
⚠️ Any existing Clouds containing dedicated (i.e., single-tenant) Kony Integration Server runtime environments will not be affected during the maintenance window (i.e., will not be automatically upgraded). If you wish to upgrade, please open a support case, specifying your Cloud(s), desired version (V8 SP4 FP3 HF7), and desired maintenance window (day, time, and timezone) when we can apply the upgrade. Existing Clouds containing shared (i.e., multi-tenant) Kony Integration Server runtime environments (e.g., AppPlatform Gold & Platinum tiers (excluding Platinum Plus), free Fabric services) will be automatically upgraded during the maintenance window.
Impact Level : minor
No downtime is expected for the impacted Cloud services while this maintenance is being performed. The scheduled maintenance is designed to mitigate disruptions to service availability and performance for the impacted Cloud services. However, it is possible for the impacted Cloud services to be unavailable and/or performance degraded for a short period of time during the maintenance window. Note that no changes are being applied for other Cloud services outside of the list of impacted services above and no service availability or performance disruption is expected for other Cloud services.