Field Notice: FN74348 - Cisco Unified Contact Center Enterprise and Cisco Cloud Connect Orchestration Feature May Fail to Connect after May 4, 2026 - Software Upgrade Recommended

Available Languages

Updated:March 18, 2026

Document ID:FN74348

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Critical

Impact Rating:

Critical

First Published:

2026-Mar-18

Last Published:

2026-Mar-18

Revision:

1.0

Cisco Bug IDs:

CSCws24436

Notice

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTY OF MERCHANTABILITY. YOUR USE OF THE INFORMATION ON THE FIELD NOTICE OR MATERIALS LINKED FROM THE FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.

Products Affected

Affected Software Product	Affected Release	Affected Release Number	Comments
Cloud Connect	12	12.6(2)
Cloud Connect	15	15.0(1)
Packaged Contact Center Enterprise	-		Releases 12.6(2) and 15.0(1) are affected.
Unified Contact Center Enterprise	-		Releases 12.6(2) and 15.0(1) are affected.

Defect Information

Defect ID	Headline
CSCws24436	Devhub upgrade is required to compliance with Cisco security standards for UCCE/PCCE CloudConnect Orchestration

Problem Description

Effective May 4, 2026, Cisco will discontinue support for API Key authentication within the Cloud Connect orchestration feature of Cisco Unified Contact Center Enterprise (UCCE) and Cisco Packaged Contact Center Enterprise (PCCE). To ensure continued access to Cisco DevHub software downloads and uninterrupted orchestration operations, customers are required to transition to Identity Token authentication.

For detailed migration instructions and the required actions, see the Workaround/Solution section of this Field Notice.

Background

On May 4, 2026, Cisco will implement a security enhancement for the Cisco DevHub software artifactory. This update requires a change to the authentication method used to access and download software for Cisco UCCE and Cisco PCCE within the Cloud Connect orchestration feature. Customers who are currently using API Key authentication must migrate to Identity Token to ensure continued orchestration functionality.

Problem Symptom

Failure to complete the required action by May 4, 2026, will result in the following service impacts:

Inability to download software: Orchestration users will be unable to access or download software packages from the Cisco DevHub.
Orchestration service disruption: Orchestration-driven patching and upgrade operations for Cisco UCCE and Cisco PCCE on Cloud Connect will fail.

Workaround/Solution

Solution

Required Actions for Devhub Authentication Migration

To maintain uninterrupted access to Cisco DevHub for Cisco UCCE and Cisco PCCE Cloud Connect orchestration, complete the following steps:

Part 1: Devhub Authentication Migration Pre-Rollout Patching (Complete Before May 4, 2026)

Install the required Engineering Special (ES) on Cloud Connect for the specific release to ensure compatibility with the new authentication method:

Note: While 15.0(1) supports Identity Token configuration without an ES, ES202511 is mandatory only for customers who use the Identity Token Auto-Rotation feature.

Part 2: Devhub Authentication Migration Post-Rollout Configuration Update (effective May 4, 2026)

After the DevHub security enhancement is live, complete the following steps in Cloud Connect publisher:

Generate Identity Token: Follow the instructions in the Generate the Artifactory Identity Token section of the proper CCE Install and Upgrade Guide.
Update Authentication Method: Change the authentication method to Identity Token using the CLI. For more information, see the CLI to Configure Authentication Method for Artifactory section of the proper CCE Install and Upgrade Guide.
Configure Credentials: Update authentication credentials with the newly generated Identity token. For more information, see the CLI to Configure Artifactory URL and Artifactory Authentication Credentials section of the proper CCE Install and Upgrade Guide.
[Optional] Enable Auto-Rotation: To automate token updates and eliminate manual intervention every six months, configure Identity Token Auto-Rotation. For more information, see the Configure Identity Token Auto Rotation section of the proper CCE Install and Upgrade Guide.

Additional Information

Note for 12.6(1) Environments: Customers who are currently running Cisco Cloud Connect Release 12.6(1) must upgrade to Release 12.6(2) and install ES04. This Engineering Special is exclusively available for Release 12.6(2) in accordance with standard product release guidelines.

Revision History

Version	Description	Section	Date
1.0	Initial Release	—	2026-MAR-18

For More Information

For further assistance or for more information about this field notice, contact the Cisco Technical Assistance Center (TAC) using one of the following methods:

Receive Email Notification About New Field Notices

To receive email updates about Field Notices (reliability and safety issues), Security Advisories (network security issues), and end-of-life announcements for specific Cisco products, set up a profile in My Notifications.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)