| Summary | This article clarifies how to create a self-signed certificate to be used in your secure application. |
|---|---|
| Environment |
Orbix 3.3 All Supported Operating Systems |
| Question/Problem Description | How do I create a self-signed certificate? |
| Clarifying Information | There are two types of CA (certificate authority) available. A commercial CA is a company that signs certificates for many systems. A private CA is a trusted node that you set up and use to sign certificates for your system only. When creating self-signed certificates we assume you will use a private CA. Please see KB article "What is a CA (certificate authority) and how do I configure my own CA used to self-sign openssl certificates?" on how to set up your own private CA |
| Error Message | |
| Defect/Enhancement Number | |
| Cause | |
| Resolution |
Once a self-signed CA has been set up and configured to be used for signing certificates, create a new CSR (certificate signing request) for e.g. the orbix certificate, which is used by the Orbix daemon: openssl req -new -config Orbix config dir/openssl.cnf -days 365 -out ./orbix_csr.pem -keyout ./orbix_pk.pem openssl ca -config Orbix config dir/openssl.cnf -days 365 -in Orbix_csr.pem -out orbix.pem To sign the certificate successfully, you must enter the CA private key pass phrase. On UNIX, do the following: On Windows, use the following command: On UNIX, to register the pass phrase used in the new certificate with the Orbix daemon, run update as follows: On Windows, run this command as follows: |
| Workaround | |
| Notes | For further details, please see chapter "Managing certificates" in the "OrbixSSL C Programmer’s and Administrator’s Guide" or "OrbixSSL Java Programmer’s and Administrator’s Guide" available at http://supportline.microfocus.com/productdoc.aspx |
| Attachment |
#Orbix
#KnowledgeDocs
#Security
#Orbix3