Signed Versus Self-Signed Certificates

Secure sockets communication can be configured using a signed certificate or a self-signed certificate. A signed certificate is an authorized certificate that is issued by a trustworthy certificate authority. A self-signed certificate is signed by the same entity whose identity it certifies. Both a signed and self-signed certificate will encrypt data communication. Using a signed certificate authority tells a customer the server information has been verified by a trusted store.
Self-signed certificates are useful for testing secure communication. They are adequate for production use in cases where encryption of the data is required, but authorization of access to the network is not required. In many installations, SPD Server is installed on an internal company network where only encryption is needed. For these cases, a self-signed certificate can be used to satisfy secure requirements.
This chapter includes examples of how to create and implement self-signed certificates to secure communication between an SPD Server and its clients. The examples use the OpenSSL cryptography toolkit. For more information, see Examples: Creating and Implementing Self-Signed Certificates for SPD Server.
Last updated: February 3, 2017