Did this article resolve your question/issue?



How to setup an SSL certificate for OpenEdge Management / OpenEdge Explorer.

« Go Back


TitleHow to setup an SSL certificate for OpenEdge Management / OpenEdge Explorer.
URL Name000044286
Article Number000166524
EnvironmentProduct: OpenEdge
Version: 10.x, 11.x
OS: All supported platforms
Other: Web Browser
Question/Problem Description
How to setup an SSL certificate for OpenEdge Management / OpenEdge Explorer.
How to use a secure connection with HTTPS to OpenEdge Management/Explorer? 
How to setup SSL connections to OpenEdge Management?
How to setup SSL connections to OpenEdge Explorer?
How to setup SSL connections to Fathom Management?
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Note: This is recommended for only development environments. For a production environment, the default SSL Server Certificate must be replaced with a fully qualified certificate from a Certificate Authority (CA).

1)  Open a proenv session
2)  cd to the OEM config directory
cd <OEMGMT>\config
3)  Create a selfsigned certificate and keystore using the Java Keytool in the DLC\jdk\bin directory.
<DLC>\jdk\bin\keytool -genkey -keyalg RSA -alias selfsigned -keystore mykeystore.jks 
-storepass password -validity 1001 -keysize 2048
In this example the alias name is selfsigned and the keystore name is mykeystore.jks the keystore password is password.

4)Export the selfsigned cert generated in step 3
<DLC>\jdk\bin\keytool -export -alias selfsigned -file selfsigned.crt -keystore mykeystore.jks

5)  Start the AdminServer
proadsv -start
6)  Use a browser to access the AdminServer on the default port of 9090.

7)  Click on the Options button located in the upper right section of the OpenEdge Management / Explorer interface.

8)  Click on the link for Web server located in the left pane of the screen.

9)  Click on the Advanced Options button

10)  Change the https port if desired and note the port number for later use.

11)  Change the Keystore path name to the file generated in step 3.

12)  Change the Keystore pass phrase to what was used in step 3.
Example using the word password:

13)  Change the alias to the alias name used in step 3.

14)  Change the alias pass phrase to the pass phrase used in step 3.
Example using the word password:

15)  Set the trusted clients (if desired) to those machines that the AdminServer will accept connections from.

16)  Click on the submit button at the top of this screen.

NOTE:  It should indicate that the configuration has been accepted and successfully updated.

It will restart the Fathom / OpenEdge Management webserver component and start it  on the port defined in step 10.

17)  Open the preferred Web Browser.  Follow the necessary instructions to import a certificate into the browser (this will vary between browsers and is outside the scope of this document).

18)  After the certificate is imported into the browser it will be possible to connect to the OpenEdge Management / OpenEdge Explorer on the port specified.
Last Modified Date12/6/2021 2:09 AM
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.