


Then, you avoid the errors on future upgrades when an appliance release changes the WebGUI certificate. The best practice is to replace the DataPower self-signed certificate with a certificate that is signed by your own organization or is signed by a certificate authority. If you use this default WebGUI SSL certificate, browsers need to accept this new, untrusted certificate before connecting. When you upgrade the DataPower appliance to release 7.2, there is a new self-signed SSL certificate for the Web Management Service.

The messages differ by browser, but you might get any of the following or other similar messages: If the appliance uses the default self-signed certificate for the Web Management Service, your browser gets an untrusted certificate message when you first connect to the WebGUI.

The signer is not included in the list of trusted third parties with internet browsers, and therefore the connection is flagged as "Untrusted". The certificate is not signed by a well-known Certificate authority (CA). DataPower release 7.2 replaces this default WebGUI SSL certificate with a new self-signed certificate. I edited my file at /etc/nginx/sites-enabled/my_site so that the top section of the server block is this.By default, the DataPower appliance uses a self-signed certificate with the WebGUI. I'm trying to set up HTTPS/SSL on my site.
