Certificate for HTTPS Communication

STA uses a digital certificate for HTTPS communication. Both the GUI and SCI use the same certificate.

SCI/GUI Certificate

Weblogic uses HTTPS for communication between the browser and server, as well as the server and SL4000 library. This requires a security certificate. You can use the auto-generated, self-signed certificate or provide a third-party signed certificate.

Auto-Generated, Self-Signed Certificate

Weblogic ships with a default 'demo' certificate which provides minimal encryption security. The STA installation automatically overwrites this certificate with an auto-generated certificate which has a 2048 bit key. The certificate is valid for 1824 days. Self-signed certificates cause most browsers to present a security exception, which the user will have to accept when connecting to the user interface.

Third-Party Signed Certificate

To eliminate the browser security exception, you can use a third-party signed certificate. The procedures for generating a third-party certificate for WebLogic can be found here: http://docs.oracle.com/cd/E13222_01/wls/docs92/secmanage/identity_trust.html

To update the certificate within WebLogic, see "Reconfigure WebLogic to Use a Different Security Certificate" in the STA Installation and Configuration Guide.