topic Re: Cisco Prime API not replying in Controllers

Cisco Prime API not replying

ChrisMac70330 — Tue, 26 Jan 2021 11:01:56 GMT

Hi,

I am having an issue with prime API, replying to me. it just stays in a state of loading but no reply.

Prime 3.6

NBI Write, NBI Credential, NBI Read are assigned to the API user.

curl -k -u API:password https://10.113.72.69/webacs/api/v1/data/InventoryDetails. -v
* About to connect() to 10.113.72.69 port 443 (#0)
* Trying 10.113.72.69...
* Connected to 10.113.72.69 (10.113.72.69) port 443 (#0)
* Initializing NSS with certpath: sql:/etc/pki/nssdb
* skipping SSL peer certificate verification
* SSL connection using TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
* Server certificate:
* subject: CN=ro-buh-pi,OU=Prime Infra,O=Cisco Systems,L=SJ,ST=CA,C=US
* start date: Jul 02 21:18:16 2020 GMT
* expire date: Sep 02 21:18:16 2039 GMT
* common name: ro-buh-pi
* issuer: CN=ro-buh-pi,OU=Prime Infra,O=Cisco Systems,L=SJ,ST=CA,C=US
* Server auth using Basic with user 'API'
> GET /webacs/api/v1/data/InventoryDetails. HTTP/1.1
> Authorization: Basic QVBJOlRFNU9hYmdDT3FCWjExbVRuVEJw
> User-Agent: curl/7.29.0
> Host: 10.113.72.69
> Accept: */*
>

Then it just freezes here,

Re: Cisco Prime API not replying

Alexander Stevenson — Tue, 09 Feb 2021 18:53:51 GMT

Hello @ChrisMac70330,

Is it possible you've left an extra period in the URL?

curl -k -u API:password https://10.113.72.69/webacs/api/v1/data/InventoryDetails. -v
> GET /webacs/api/v1/data/InventoryDetails. HTTP/1.1

I'm not accustomed to seeing periods at the ends of URLs, and that includes cURL requests.

Re: Cisco Prime API not replying

Alexander Stevenson — Tue, 09 Feb 2021 18:56:38 GMT

Also, here's the Cisco Prime Infrastructure 3.6 API Reference Guide, in case you didn't have it.

Re: Cisco Prime API not replying

ChrisMac70330 — Wed, 10 Feb 2021 07:15:27 GMT

Hi, no the . is there just very small. I have read and followed the guide, but it's not working even in postman.

I really do not understand why it would not work, read about having chrome opened so you bypass the invalid certificate but even from local computer bash is not working.

* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
* CAfile: C:/Program Files/Git/mingw64/ssl/certs/ca-bundle.crt
* CApath: none
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [85 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [920 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [333 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [70 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server did not agree to a protocol
* Server certificate:
* subject: C=US; ST=CA; L=SJ; O=Cisco Systems; OU=Prime Infra; CN=ro-buh-pi
* start date: Jul 2 21:18:16 2020 GMT
* expire date: Sep 2 21:18:16 2039 GMT
* issuer: C=US; ST=CA; L=SJ; O=Cisco Systems; OU=Prime Infra; CN=ro-buh-pi
* SSL certificate verify result: self signed certificate (18), continuing anyway.
* Server auth using Basic with user 'API'
} [5 bytes data]
> GET /webacs/api/v1/data/InventoryDetails. HTTP/1.1
> Host: 10.113.72.69
> Authorization: Basic QVBJOlRFNU9hYmdDT3FCWjExbVRuVEJw
> User-Agent: curl/7.73.0
> Accept: */*