2.11 CCO user authentication failed in SW Updates/Server Connection
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-26-2024 06:37 AM
Recently installed 2.11 and cannot configure Software Update/Server Connection as when I add my CCO credentials (checked a couple of times and it's correct), get the error below:
Failure
Validation of credentials failed, Please try again.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2024 06:14 AM
I flagged this in a post back at the start of May 2024 (Issues with entering CCO details in CSPC 2.11 - Cisco Community) I've been attempting to work with the assigned engineer on getting this resolved as configuring details either via the GUI or the CLI result in the same issue.
I've been chasing the problem now for about 8 weeks without any resolution to the issue. Initially it was advised it was an API issue and that I needed to escalate to the Cisco API team. Then was advised this was an error in understanding by the engineer and it wasn't an API issue. He advised he would look into it further but had radio silence since. Have been chasing every couple of weeks for an update without response.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2024 07:18 AM
I just updated to 2.11.0.1 and have the same issue. And also, still radio silence from Cisco.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2024 07:52 AM
I was able to enable the connection via the CLI Only. There is a different process compared to previous versions. You have to copy out a URL and register it via CCO logon within something like 120 seconds. CLI Command is
conf server enable
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-05-2024 01:51 PM
Thanks that was helpful, as I've been struggling with the same issue.
![](/skins/images/5BCFDE0138A9573C8EB2CB0A1DB573AC/responsive_peak/images/icon_anonymous_message.png)