The system supports the following types of code-signing certificates: The message informs the user that the applet is signed by a trusted authority. As a result, if a user requests a potentially high-risk applet, the user’s Web browser displays an informational message instead of a warning. If you import a code-signing certificate, Connect Secure uses the imported certificate to re-sign applets instead of the default self-signed certificate. As a result, if a user requests a potentially high-risk applet (such as an applet that accesses network servers), the user’s Web browser alerts him that the root is untrusted. ![]() This certificate is issued by a nonstandard trusted root CA. ![]() When Connect Secure intermediates a signed Java applet, it re-signs the applet with a self-signed certificate by default. If the basic certificates do not meet your needs, however, you may install multiple device and applet certificates on Connect Secure or use trusted CA certificates to validate users. Connect Secure can use a single code-signing certificate to resign all Java applets and a single device certificate to intermediate all other PKI-based interactions. In a basic setup, the only required certificates are a device certificate and a code-signing certificate. You are here: Understanding Code-Signing CAs
0 Comments
Leave a Reply. |