Keystores and key entries

To implement HTTPS for FMS, you must generate a keystore and key entry, and then generate a certificate signing request (CSR) from the private key. Siemens Digital Industries Software recommends using a trusted certificate, purchased from a third-party vendor, when configuring FMS to use HTTPS. Note The certificate authority's root certificates for your purchased certificates must include standard distributions of Sun Microsystems' Java run-time environment. This is usually the case for certificates purchased from well-known certificate authorities. Use the following elements to create a keystore. Element Description keystore Specifies the keystore file name. This is the Java-based storage standard. Public and private keys are stored in an encrypted keystore. Individual keys within this cryptographic storage may also have individual password protection. keystore.password Specifies the keystore password. The password is required to open or manage the keystore. The standard entry is changeit. FSC_myhost Specifies an alias name for the certificate. The certificate is bound to the host; name it accordingly. A similar convention FSC_host_userid is used by installers to name configuration files. FSC_myhost.password Specifies the certificate (alias) password required to retrieve the certificate. FSC_myhost.csr Specifies the name of the certificate signing request (CSR) file. The file contains the CSR information and is sent to the signing authority. FSC_myhost.cer Specifies the certificate file. This is the file returned by the signing authority. Use the trusted certificate to create a keystore in your FSC_HOME directory.