V8 SP4 FP3 Engagement Release and Hotfixes for Other Components

• Cloud Management Console

  • Fix inability to add operations in AWSAPIGateway Connector in Integration services that affected some AWS regions

  • Fix inability to reconfigure url & other properties in the ‘Publish and Reconfigure’ if the services are protected by Identity Service

• Workspace

  • Fix inability to delete or edit name of Identity service. In cases when the Identity service cannot be deleted, notify user and provide more detailed information explaining the cause of the failure.

  • Fix issue in which JSONPath property in a service definition should be added only for Integration Services of type ‘Mock Data’ and not for all service types. It was being wrongly added for all service types, if they have a stub template defined in the operation

• Engagement

  • Enhance Fetch All Messages API to include additional filters for status and lastUpdatedDate

  • Introduce performance improvements in Push Message request cancellation and Subscription APIs

  • Fix additional miscellaneous bugs and improve overall stability

• Identity

  • Fix several HTTP 500 errors occurring due to profile API invocation

  • Enhance SAML logout

  • ⚠️ For customers who have dedicated Identity services, we will start to apply the Identity services upgrade during this maintenance window, but expect to complete for all customers’ dedicated Identity services over the next few weeks. In general, we do not expect impacts to your Identity services during the upgrade process. If we believe there may be any impacts during your Identity services upgrade, we will notify owners and admins in your Cloud account(s) via support case to communicate any impacts and coordinate on a suitable upgrade window

• Kony IQ

  • Defect fixes and stabilization

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.

V8 SP4 FP3 Release

• Cloud Management Console

  • Re-configuration support for Object Services in the ‘Publish and Configure’ flow

  • Service Configuration (Identity, Integration, and Object Services) export and import from the Fabric Console for a Fabric application and environment

  • Audit Logs can now be accessible from the Apps Listing, Services Listing pages in the Fabric Console

  • Ability to configure display name for the Client Binaries in the Fabric Console, which will be reflected in the Enterprise Store

  • Ability to configure response output parameters in the Integration Services to follow hierarchy and have same name for record(s) / collection(s)

  • Defect fixes and stabilization

• Workspace

  • Support for the Cloud Management Console changes listed above

  • ⚠️Workspace services will be unavailable for a portion of the maintenance window. During the maintenance window, please refrain from any activities, which would use Workspace services (e.g., publishing)

• Developer Portal

  • Upgraded versions Log JARS

  • Defect fixes and stabilization

• Identity

  • Defect fixes and stabilization

  • ⚠️ For customers who have dedicated Identity services, we will be beginning to apply the Identity services fixpack upgrade during this maintenance window, but expect to complete for all customers’ dedicated Identity services over the next few weeks. In general, we do not expect impacts to your Identity services during the upgrade process. If we believe there may be any impacts during your Identity services upgrade, we will notify owners and admins in your Cloud account(s) via support case to communicate any impacts and coordinate on a suitable upgrade window

• Kony IQ

  • Defect fixes and stabilization

• Integration Server

  • Defect fixes and stabilization

  • The new version will be available on June 10 for customers who are interested in upgrading their Clouds

  • ⚠️ Any existing Clouds containing 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), and desired maintenance window (day, time, and timezone) when we can apply the upgrade

We anticipate that Workspace services will be unavailable for a portion of the maintenance window. No downtime is expected for the remaining set of 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.

Identity Services Release

• Identity services

  • Add browser session logout support for SAML identity services

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.

Cloud Management Console Release

• Cloud Management Console

  • During the save of an operation, the latest metadata was being fetched from the backend by the Console, which would not necessarily be able to connect over VPN or whitelisted to connect to the backend. To address this issue, all API invocations fetching metadata when an environment has been specified have been delegated to the Kony Server APIs, which would be able to connect over VPN or whitelisted to connect to the backend.

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.

Reporting Services delayed processing of Integration Server analytics

• Cloud Analytics

The processing of analytics for Kony Integration Server has been paused starting at May 17, 2019 16:35 PM UTC. Analytics from this time forward will be delayed when generating reports. We have identified an issue in our analytics processing and are working toward a solution. Once the issue has been addressed, we will be able to start processing the backlog of analytics since processing was paused. Analytics beyond Kony Integration Server are still being processed and would still be available within reports.

[2019-05-22 13:15 UTC] The backlog of analytics data has not yet been fully processed. At the current file count and processing rate, we estimate that it will be processed by May 24 15:00 UTC. We will continue to monitor and provide updates until the backlog has been fully processed and data can be made available within reports.

[2019-05-23 15:20 UTC] We are continuing to process the backlog of analytics data (oldest data that has not yet been processed being approximately 44 hours old). At the current file count and processing rate, we estimate that the backlog (along with processing of current inbound analytics data) will be completed and caught up by May 24 21:00 UTC. We are continuing to monitor and will continue to provide updates until the backlog has been fully processed and all data would be expected to be available within reports.

[2019-05-24 15:30 UTC] We have processed 80% of the backlog. Messages are still approximately 24hrs behind in processing. At the current processing rates, we expect to be caught up to normal latency by May 25 15:30 UTC.

[2019-05-27 11:00 UTC] Resolved. Analytics has completed processing the backlog of data and is now running with normal latency.

Cloud Management Console Release

• Cloud Management Console

  • Fix inability to import views as Object in Fabric

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.

Identity Services Release

• Identity services

  • Fix for Azure SAML login failure: No Local Entity id found for alias http:/100000002.12efaf

  • Add support for returning custom user attributes as part of OIDC provider profile API response

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.

Cloud Services - Increased error rates

• Fabric Services

• Multi-tenant services

[22:16 UTC] We have detected an increase in latency and error rates on the responses from our cloud services. Our cloud hosting provider is currently investigating issues with the content delivery network that Kony leverages. See the AWS status page for the very latest information : https://status.aws.amazon.com/

[22:59 UTC] Resolved Between 22:16 and 22:43 UTC our cloud hosting provider has identified increased error rates for requests served by edge locations in South East Asia. The issue has been resolved. Performance and error rates have improved back to expected levels.

Cloud SSL Certificate Update for Engagement services in all regions except Oregon

• Cloud SSL certificate for Engagement services (*.messaging.konycloud.com) in all regions except Oregon, which expires on May 9, 2019 at 12:00 PM UTC. We will be rotating starting on May 9, between 00:01 and 04:00 UTC.

• ⚠️ Note: If you are not using Engagement services in a non-Oregon region and have not pinned the Engagement Kony certificate (*.messaging.konycloud.com) in your application, no application updates will be necessary. Customers that have pinned this SSL certificate will need to download the new certificate, rebuild their application(s), including both the old and new certificates, and publish the updated binaries to the various app stores. Your application(s) should be published before Kony updates the certificates on the Cloud servers or customers will no longer be able to connect. A new certificate can be found on the Kony Cloud Certificate Preview page. The new certificate can also be downloaded by executing the following command:

  • Engagement: openssl s_client -showcerts -connect konycertificatepreview.messaging.konycloud.com:7443

• Customers who have pinned the public key instead of the full certificate may not be required to update their applications as we would try to preserve the same public key for the new certificate(s) as the old certificate(s).

• If necessary, you can submit your applications for expedited approval (e.g., Apple has an expedited approval process for critical bugs, or in this case, pinned certificates).

Customer applications that have pinned the SSL certificate will need to be updated as described above prior to this maintenance window. Customer applications that have not pinned this SSL certificate will not be affected and will experience no service disruptions during this maintenance window.

You can also refer to Kony Base Camp for more general information regarding how to enable SSL pinning in your apps.

Note that SSL certificates for other Kony Cloud services (e.g., Identity, Fabric, Sync) expire on November 21, 2019. You can verify by inspecting the certificates, which are available on the Certificate Preview site. We will send a reminder in advance of the next rotation for these certificates so you can prepare.