01.06.2013 Views

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

OpenEdge Getting Started: Installation and Configuration - Product ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Managing certificate stores for <strong>OpenEdge</strong> clients <strong>and</strong> servers<br />

• -remove alias ... — Removes one or more specified (alias) certificate<br />

store entries<br />

For more information on the options <strong>and</strong> functions of the certutil comm<strong>and</strong>-line<br />

utility, see Appendix C, “Comm<strong>and</strong> <strong>and</strong> Utility Reference.”<br />

Using mkhashfile to install root certificates in the<br />

<strong>OpenEdge</strong> root certificate store<br />

The mkhashfile comm<strong>and</strong>-line utility provides a simple way to install a root certificate<br />

that is authorized by your own internal-use CA, or any CA that can provide you with a<br />

PEM-encoded certificate (typically in a file named with the .pem extension). If you are<br />

using your own certificate server to provide the certificate, refer to the documentation<br />

for the certificate server administration software for information on how to obtain<br />

PEM-encoded certificates. Once you have the certificate accessible to your <strong>OpenEdge</strong><br />

SSL client machine, you can use the mkhashfile comm<strong>and</strong>-line utility to install it in the<br />

<strong>OpenEdge</strong> root certificate store.<br />

Note: If the root certificate is not a PEM-encoded certificate, it is recommended that<br />

you use the certutil comm<strong>and</strong>-line utility, specifying the format option. For<br />

details about the certutil comm<strong>and</strong>-line utility <strong>and</strong> all its options <strong>and</strong> functions,<br />

see the detailed syntax information for the certutil comm<strong>and</strong> listed in<br />

Appendix C, “Comm<strong>and</strong> <strong>and</strong> Utility Reference.”<br />

To use mkhashfile to create an entry in the <strong>OpenEdge</strong> root certificate store for a local<br />

PEM-encoded certificate file, vsigntca.pem, specify the file with the mkhashfile<br />

comm<strong>and</strong> that you enter in the <strong>OpenEdge</strong> Proenv comm<strong>and</strong> window. For example:<br />

proenv>mkhashfile vsigntca.pem<br />

<strong>OpenEdge</strong> Release 11.0 as of Fri Oct 14 00:15:12 EST 2011<br />

Running SSLC comm<strong>and</strong> ...<br />

Copying vsigntca.pem <strong>and</strong> 18d46017.0 to C:\Progress\<strong>OpenEdge</strong>\certs<br />

proenv><br />

The utility generates the entry as a file with an encrypted filename, 18d46017.0, which<br />

is the alias used to identify the certificate store entry. You can then manage this entry<br />

along with all other entries in the <strong>OpenEdge</strong> certificate store using the certutil utility.<br />

For more information see the “Using certutil to manage an <strong>OpenEdge</strong> root certificate<br />

store” section on page 268.<br />

For more information on the mkhashfile comm<strong>and</strong>-line utility, see Appendix C,<br />

“Comm<strong>and</strong> <strong>and</strong> Utility Reference.”<br />

<strong>OpenEdge</strong> <strong>Getting</strong> <strong>Started</strong>: <strong>Installation</strong> <strong>and</strong> <strong>Configuration</strong> 269

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!