IÕm in the process of swapping out a current Verisign issued certificate, issued for company1.com, for another Verisign issued certificate for company2.com. When I submitted the csr to Verisign, I specified that the certificate was for a Netscreen type device. IÕve just read the SSL VPN admin guide, and found that it should have been specified as an Apache type. Will there be issues if I attempt to import and use it? Should I just attempt to get Verisign to issue another, as type Apache?
Solved! Go to Solution.
Hi Christ,
No issue in this kind of situation :
You need 3 things to be okay with the certificate :
- The certificate need to be signed by a public CA ( Like VerySign )
- The certificate must be up to date ( Valid From and Valid to date )
- The URL of your secure access ( like myportal.mycompany.net ) must be equals to the certificate DN
When i m generation CSR for SSL box i use a "Web Server" type and it works too :-)
Hi Christ,
No issue in this kind of situation :
You need 3 things to be okay with the certificate :
- The certificate need to be signed by a public CA ( Like VerySign )
- The certificate must be up to date ( Valid From and Valid to date )
- The URL of your secure access ( like myportal.mycompany.net ) must be equals to the certificate DN
When i m generation CSR for SSL box i use a "Web Server" type and it works too :-)
If you have any Linux systems around, you also can use openssl to convert between several different certificate types. I had an Apache cert from Verisign that I needed to change to IIS and openssl did the trick.
Ray
I was able to install and use the certificate without any issues. Thanks for your advice.
Chris