"CA=TRUE" means that the certificate is a CA and can sign other certificates. If your CA signed the CSR with that constraint, then either it was included in the CSR itself (meaning the CSR asked the CA to make the constraint true) or the constraint was overridden by the CA when it signed the certificate.
It sounds like whatever application you are working with specifically does not want the certificate to be able to sign other certificates, but that's about all I can say without additional information/context for the error. What application generated this error message and what procedure were you completing when it appeared?
i m working on cisco expressway C , this Analysis comes from expressway C , i use internel CA ( IOS Router acting CA) to sign the server certificate of Expressway C and E
using https://cway.cisco.com/csa/ to analyse my expressway C diagnostic log
I've done IOS-signed certificates in a lab and had Jabber register via MRA. The Jabber client asks the user to trust the 'self-signed' Expressway-E certificate, after which they will connect through. I've never tried physical devices, though, and can easily see where they would not be able to connect since they can't do so. Thanks, Jonathan.
Hi Maren , Hi Jonathan
thanks for reply
pls can u help in the below thread , i didnt find such issue , i read carefully what in TS section in BRKCRT-2602