I have an existing SSL certificate which I'm trying to also use for my rv345 router (e.g. I don't want to use the rv345 to create the CSR as shown here (https://www.cisco.com/c/en/us/support/docs/smb/routers/cisco-rv-series-small-business-routers/smb5855-replace-self-signed-certificate-on-the-rv34x-router.html)
The only way I seem to be able to import my certificate and intermediate certificates is to (using pem files)
1) Concatenate the Certificate + the 3 chain files into one bundle file (certificate first)
2) Using openssl convert the pem files to pkcs12 with this command:
openssl pkcs12 -export -out certificate.pfx -inkey privateKey.key -in bundle.crt
3) log into my rv345 Go to Administration->Certificates->Import Certificate
4) Select pkcs12 encoded file, choose certificate.pfx and enter in the password I created for the file
5) Everything seems to work fine, and In the list of imported certificates (see attached screen shot) I now see a local certificate and a CA certificate are both imported
However when I set my VPN to then use this newly imported ssl certificate, I notice the chain file isn't properly imported; I can tell this because when I go to https://www.sslshopper.com/ssl-checker.html It shows me that the ssl cert is somewhat installed correctly but is missing intermediate certs (see other screen shot). AnyConnect windows clients can connect, mac os x catalina clients get the "Cannot verify gateway" error message mentioned in the community link below. Both clients seem to think it's a trusted cert.
Any ideas how to fix this? I think it's causing a VPN connection error on Mac OS X catalina for anyconnect clients (as discussed here https://community.cisco.com/t5/vpn/anyconnect-got-an-error-after-updating-macos-catalina/td-p/3937692)
