IOS and ASA use the same trustpoint model for storing certificates in the configuration. A trustpoint just a container in which certificates are stored. A trust point can hold up to two certificates.
An identity certificate (a certificate that the router owns the corresponding private key)
A certificate authority certificate (a certificate that is signed by another party. The router doesn't own the matching private key)
Once a certificate has been generated and installed into a device it is possible to export the whole certificate chain and private key pair for storage in a secure location. It is important to backup up identity certificates in case of device failure. In a case where you have control over the certificate authority it is trivial to issue another certificate but in cases where there are financial costs (i.e. a certificate issued from Verisign, Thawte, GoDaddy, etc) to reissue another certificate it may be beneficial to import the backed up certificate into the new device.
To backup a certificate via the command line do the following, where TrustPoint1 is the trust point name and cisco123 is the password used to encrypt the output:
ciscoASA(config)# crypto ca export TrustPoint1 pkcs12 cisco123
This will output a long text string. That is a base64 encoded pkcs12. A pkcs12 is a standardized container that carries the identity certificate, it's matching private key, and all the remaining certificates within the chain. Below is an example of the output you should see
ciscoASA(config)# crypto ca import TrustPoint2 pkcs12 cisco123
<paste in the base64 encoded pkcs12>
You can verify the installation by issuing the command "show crypto ca certificates"
RSA keys are stored in the flash in a hidden partition that can not be accessed. On IOS at time of RSA key generation the exportable keyword must be specified. Otherwise the router will be unable to export the key, making the pkcs12 export fail. ASA RSA keys are always exportable and do not have this limitation.
I'm pretty sure the answer to this is no, but I'd like to check just in case there's a workaround. Is it possible for the management interface to be shared with the SFR module, so I can manage the ASA via SSH / ASDM via an IP on the management interf...
Is there a way to extend logging for radius logs on ISE 2.6? I have tried going to admin -> logging -> log settings and changing the default to 30 days but my live logs for radius do not appear to be using that setting. I also tried pointing ISE to ...
Hello! We have Cisco ASA 5525 in Failover mode (Active/Passive) (SW 188.8.131.52), 4 RDP Servers based on WinServer 2012R2(Serv_Net sec level 50), PCs connected to ASA (PC_Net, sec level 50) and uplink to Corporate Networks (CORP_NET, sec level 0). W...