What do I do if when I log in to the SMA appliance my browser gives me an error, or if my Java components give me an error?
Answer: These errors can be caused by any combination of the following three factors:
- The certificate in the SMA appliance is not trusted by the browser
- The certificate in the SMA appliance could be expired.
- The site requested by the client Web browser does not match the site name embedded in the certificate.
Web browsers are programmed to issue a warning if the previous three conditions are not met precisely. This security mechanism is intended to ensure end-to-end security, but often confuses people into thinking something is broken. If you are using the default self-signed certificate, this error appears every time a Web browser connects to the SMA appliance. However, it is just a warning and can be safely ignored, as it does not affect the security negotiated during the SSL handshake. If you do not want this error to happen, you should purchase and install a trusted SSL certificate onto the SMA appliance.
I get the following message when I log in to my SMA appliance – what do I do?
Answer: It’s the same problem as noted in the previous topic, but this is the new “improved” security warning screen in Microsoft Internet Explorer. Whereas before IE5.x and IE6.x presented a pop-up that listed the reasons why the certificate is not trusted, IE simply returns a generic error page which recommends that the user close the page. The user is not presented with a direct ‘Yes’ option to proceed, and instead must click on the embedded Continue to this Website (not recommended) link. For these reasons, it is strongly recommended that all SMA appliances, going forward, have a trusted digital certificate installed.
I get the following message when I log in to my SMA appliance using Firefox– what do I do?
Answer: Much like the errors shown previously for Internet Explorer, Firefox has a unique error message when any certificate problem is detected. The conditions for this error are the same as for the previous Internet Explorer errors.
To get past this screen, click the Or you can add an exception link at the bottom, then click Add Exception that appears. In the Add Security Exception window that opens, click Get Certificate, ensure that Permanently store this exception is checked, and finally, click Confirm Security Exception. See the following:
To avoid this inconvenience, it is strongly recommended that all SMA appliances, going forward, have a trusted digital certificate installed.
When I launch any of the Java components it gives me an error – what should I do?
Answer: See the previous section. This occurs when the certificate is not trusted by the Web browser, or the site name requested by the browser does not match the name embedded in the site certificate presented by the SMA appliance during the SSL handshake process. This error can be safely ignored.
Do I have to purchase a SSL certificate?
Answer: Although the level of encryption is not compromised, users accepting an untrusted certificate introduces the risk of Man-in-the-Middle attacks. SonicWall Inc. recommends installing only trusted certificates or installing the default self-signed certificate in all the clients.
What format is used for the digital certificates?
Are wild card certificates supported?
What CA’s certificates can I use with the SMA appliance?
Answer: Any CA certificate should work if the certificate is in X509v3 format, including Verisign, Thawte, Baltimore, RSA, and so on.
Does the SMA appliance support chained certificates?
Answer: Yes, it does. On the System > Certificates page, complete the following:
- Under “Server Certificates,” click Import Certificate and upload the SSL server certificate and key together in a .zip file. The certificate should be named ‘server.crt’. The private key should be named ‘server.key’.
- Under “Additional CA Certificates,” click Import Certificate and upload the intermediate CA certificate(s). The certificate should be PEM encoded in a text file.
After uploading any intermediate CA certificates, the system should be restarted. The web server needs to be restarted with the new certificate included in the CA certificate bundle.
Any other tips when I purchase the certificate for the SMA appliance?
Answer: We recommend you purchase a multi-year certificate to avoid the hassle of renewing each year (most people forget and when the certificate expires it can create an administrative nightmare). It is also good practice to have all users that connect to the SMA appliance run Windows Update (also known as Microsoft Update) and install the ‘Root Certificates’ update.
Can I use certificates generated from a Microsoft Certificate Server?
Answer: Yes, but to avoid a browser warning, you should install the Microsoft CA’s root certificate into all Web browsers that connect to the appliance.
Why can’t I import my new certificate and private key?
Answer: Be sure that you upload a .zip file containing the PEM formatted private key file named “server.key” and the PEM formatted certificate file named “server.crt.” The .zip file must have a flat file structure (no directories) and contain only “server.key” and “server.crt” files. The key and the certificate must also match, otherwise the import fails.
Why do I see the status “pending” after importing a new certificate and private key?
Answer: Click the ‘configure’ icon next to the new certificate and enter the password you specified when creating the Certificate Signing Request (CSR) to finalize the import of the certificate. After this is done, you can successfully activate the certificate on the SMA appliance.
Can I have more than one certificate active if I have multiple virtual hosts?
Answer: It is possible to select a certificate for each Portal under the Portals > Portals| Edit Portal - Virtual Host tab. The portal Virtual Host Settings fields allow you to specify separate IP address, and certificate per portal. If the administrator has configured multiple portals, it is possible to associate a different certificate with each portal. For example,
sslvpn.test.sonicwall.com might also be reached by pointing the browser to
virtualassist.test.sonicwall.com. Each of those portal names can have its own certificate. This is useful to prevent the browser from displaying a certificate mismatch warning, such as “This server is abc, but the certificate is xyz, are you sure you want to continue?”
I imported the CSR into my CA’s online registration site but it’s asking me to tell them what kind of Webserver it’s for. What do I do?
Answer: Select ‘Apache.’
Can I store the key and certificate?
Answer: Yes, the key is exported with the CSR during the CSR generation process. It’s strongly recommended that you can keep this in a safe place with the certificate you receive from the CA. This way, if the SMA appliance ever needs replacement or suffers a failure, you can reload the key and cert. You can also always export your settings from the System > Settings page.
Does the SMA appliance support client-side digital certificates?
Answer: Yes, client certificates are enforced per Domain or per User on the Users > Local Users: Edit User – Login Policies tab.
- Per Domain/Per User client certificate enforcement settings:
- Option to Verify the username matches the Common Name (CN) of the client certificate
Option to Verify partial DN in the client certificate subject (optional). The following variables are supported:
Domain name: %USERDOMAIN%
Active Directory username: %ADUSERNAME%
- Support for Microsoft CA Subject Names where CN=<Full username>, for example CN=John Doe. Client certificate authentication attempts for users in Active Directory domains should have the CN compared against the user’s full name in AD.
- Detailed client certificate authentication failure messages and log messages are available in the Log > View page.
- Certificate Revocation List (CRL) Support. Each CA Certificate now supports an optional CRL through file import or periodic import through URL.
The client certificate must be loaded into the client’s browser. Also, remember that any certificates in the trust chain of the client certificates must be installed onto the SMA appliance.
When client authentication is required my clients cannot connect even though a CA certificate has been loaded. Why?
Answer: After a CA certificate has been loaded, the SMA appliance must be rebooted before it is used for client authentication. Failures to validate the client certificate also causes failures to logon. Among the most common are certificate is not yet valid, certificate has expired, login name does not match common name of the certificate, certificate not sent.