topic Re: api/v1/certs/system-certificate/export throws could not prepare s in Network Access Control

API /system-certificate/export throws could not prepare statement erro

prathwishhegde — Tue, 23 May 2023 04:04:40 GMT

The Above Post API response from the Cisco ISE v3.1.0.518 is not consistent. Out of 6 tries 1 API request is failing with the below exception. (Same API test with same payload)

2023-05-22 13:53:31,914 ERROR [openapi-http-pool8][] com.cisco.epm.ssl.SSLManagerFactory -::::- Error in creating trust manager factory
com.cisco.cpm.edf2.na.EDFNetworkDeviceException: org.hibernate.exception.GenericJDBCException: could not prepare statement
at com.cisco.cpm.infrastructure.certmgmt.helpers.CertMgmtEDFHelper.getAllTrustCerts(CertMgmtEDFHelper.java:38)
at com.cisco.cpm.infrastructure.certmgmt.im.TrustCertificate.getAllTrustCertificates(TrustCertificate.java:29)
at org.apache.tomcat.util.net.jsse.IseTrustStoreLoader.getAllTrustCerts(IseTrustStoreLoader.java:116)

Re: api/v1/certs/system-certificate/export throws could not prepare s

Arne Bier — Mon, 22 May 2023 20:24:25 GMT

Normally when asking a question on these forums, we don't just dump a long list of errors and expect an answer. You might start with a simple intro and some commands (if you expect others to try it on their systems to see if they can also see the same error).

And what version of ISE etc.

If it's a software defect on a production system you should also open a TAC case (if you haven't already done so.)

Re: api/v1/certs/system-certificate/export throws could not prepare s

prathwishhegde — Tue, 23 May 2023 04:05:45 GMT

@Arne Bier The Above Post API response from the Cisco ISE v3.1.0.518 is not consistent. Out of 6 tries 1 API request is failing with the exception shared above. (Same API test with the same payload)

Re: api/v1/certs/system-certificate/export throws could not prepare s

Greg Gibbs — Tue, 23 May 2023 06:14:57 GMT

I'm unable to replicate any issues with the '/api/v1/certs/system-certificate/export' POST API call in my ISE 3.1 patch 6 instance.

I tried with both export options..
"export": "CERTIFICATE_WITH_PRIVATE_KEY" (specifying the password key/value)
"export": "CERTIFICATE"

I executed the API call 10 times in a row with both export option and the response for each iteration was 200 OK. I tested using both Postman and the built-in Swagger UI with the same results.

If you're running the latest patch, you will likely need to open a TAC case to investigate further.