Hi @Jasoncull365 Yes, your certificate (the public key) needs to be signed by a public CA, GoDaddy in your case. If you're going to buy a wildcard cert then there is no need to add additional FQDN's to the cert as the wildcard cert will enable authenticated communication to *.companyname.com.au. As soon as you have the signed cert, you need to upload it and also the private key to your firewall. In addition to that you also need to upload the GoDaddy intermediate CA cert to the firewall (and if there are more intermediates between your wildcard cert and the root you also have to upload them). This way the firewall is able to build ther certificate path up to the root CA. In addition, uploading the intermediate CA certs, will tell the firewall which certificates need to be sent in the TLS handshake to a client. The sending of the additional certs to the client is needed that also it will be able to build the certificate path up to the root (the client normally only has the root CA cert in his trust store, but not the intermediate CA certs) and can verify the identity of your certificate - without this verification the clients will see a certificate warning in their browsers. Your wildcard cert then needs to be added to a SSL/TLS profilw, which you then could reference in the global protect gateway and portal configuration. Hope this helps a little. Regards, Remo
... View more