cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
870
Views
0
Helpful
5
Replies

Update to Service Account credential causing Dialer Import API error

leonardjam1
Level 1
Level 1

We've got a 12.5.1 PCCE 4k instance and we're updating the primary service account, just the password.  I've made the update in the Service Account Manager on the Roggers and AWs, updated it in the inventory for the CVPs and the credentials used in Finesse.  After restarting all servers (Roggers, PGs, AWs, CVPs...) an API import job starts failing in Postman:

POST https://j-lab1-01aw01.domain/unifiedconfig/config/campaign/5006/import

 

 
<apiErrors>
    <apiError>
        <errorMessage>The user name or password for the web service /icm-dp/rest/DiagnosticPortal/ListProcesses at j-lab1-01call1a:7890 is not correct.</errorMessage>
        <errorType>errorConnectDiagPortal.incorrectUsernameOrPassword</errorType>
    </apiError>
</apiErrors>

This is a "lab" as it's our dev environment, but it's a fully deployed 4k PCCE.  Same issue occurred in our Prod implementation.  It's interesting that it calls out the Diag Portico access, that URL "https://j-lab1-01call1a.domain:7890/icm-dp/rest/DiagnosticPortal/ListProcesses"  resolves just fine with the new service account credentials.

Other API calls, like a GET for campaign stats have no issue.  Swapping the service account password back fixes this.  TAC tried but we weren't successful in repairing what's going on.  All other operations, to the best of my testing, are working fine.

Anyone ever run into anything similar? 

2 Accepted Solutions

Accepted Solutions

srivacha
Cisco Employee
Cisco Employee

@ leonardjam1 Internally, we use the credentials associated with the Principal AW to make Diagnostic Portal API calls to all the CCE machines in the deployment.

You mentioned that you have updated the password for the CVPs in the inventory. Can you also cross check the Administrator password that is supplied for the AW machines in the inventory?

View solution in original post

Hello @srivacha , thank you for the suggestion, I had not done that step.  I assumed (possibly incorrectly) that the pw would be updated from the Service Account Manager but I am will to try anything at this point.  Thanks, I'll follow up as soon as I can try that.

View solution in original post

5 Replies 5

Janos Benyovszki
Cisco Employee
Cisco Employee

@ leonardjam1 sorry, but I could not find the Dialer Import API on the Contact Center API page here https://developer.webex-cx.com/documentation/getting-started , which is what we could help here. Is it there and I just missed it? Do you have a reference page for it?

Hello Janos, thank you for the reply.  I'll be sure to look through this info, the guide I'd been using is
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/icm_enterprise/icm_enterprise_12_5_1/program/guide/ucce_b_cisco-unified-contact-center-enterprise_developer_guide_12_5/ucce_b_cisco-unified-contact-center-enterprise_deve...
I'll continue to comb through the info, it's just a very odd result to fail a API call after successfully changing the credentials (at least everywhere I've been told to change it)

srivacha
Cisco Employee
Cisco Employee

@ leonardjam1 Internally, we use the credentials associated with the Principal AW to make Diagnostic Portal API calls to all the CCE machines in the deployment.

You mentioned that you have updated the password for the CVPs in the inventory. Can you also cross check the Administrator password that is supplied for the AW machines in the inventory?

Hello @srivacha , thank you for the suggestion, I had not done that step.  I assumed (possibly incorrectly) that the pw would be updated from the Service Account Manager but I am will to try anything at this point.  Thanks, I'll follow up as soon as I can try that.

@srivacha That did appear to correct the issue.  Thank you, I did run into a bug when doing the inventory updates where the upload threw an error about my CUIC VMs.  My TAC case engineer found a bug that just has you remove the peripherals and only update the servers you need to.  Thanks again, I'm going to do a few more tests to ensure this repairs it in prep for our prod environment.