Secure server connections to .NET Open Clients
- Last Updated: March 18, 2026
- 2 minute read
- OpenEdge
- Version 13.1
- Documentation
.NET Open Clients securely connect to ABL application servers using HTTPS (Hypertext Transfer Protocol Secure) connections. This protocol encrypts data sent between clients and application servers. To encrypt the data, the clients and servers must share a certificate. TLS (Transport Layer Security) is configured on the application server by the system administrator. The system administrator supplies the necessary certificate files used to verify that the server is a trusted application server.
For more information on how to set up server security, see Use TLS in PAS for OpenEdge in Manage Progress Application Server (PAS) for OpenEdge. Client developers must then import the server certificates into their client keystore.
Import server certificates on .NET Open Clients
.NET Open Clients use the .NET Framework certificate management systems.
- Search for:
- Manage User Certificates in the for user certificates. The utility opens.
- Manage computer certificates in the for computer certificates. The utility opens.
- Create or select the folder where you want to store your server certificates.
- Right-click to select .
- Locate and import your certificate.
- When clients connect to the application server using
HTTPS, the keystore is automatically checked for a valid server certificate.
Certificates for development and test systems
OpenEdge ships a small set of root digital certificates from leading industry Certificate Authorities (CAs) with the Open Client Toolkit. These digital certificates are intended only for use during development and test cycles. Production systems should use certificates from a trusted Certificate Authority.
The certificate files included with the Open Client Toolkit are stored in .zip and .jar files
called certificate store files, typically located under
%DLC%/certs. To use these certificates with .NET Open
Clients in development and test environments, extract the required CA certificates
and import them into the appropriate Windows certificate store using the Windows
certificate management tools (for example, certmgr or
certlm). The .NET Open Clients rely on the OS-managed
Windows certificate store as their default trust model.
Each certificate store file holds several individual root digital
certificates and contains one digital certificate list (.dcl file) that lists all certificate files stored in the file.
The individual certificates have one of the following formats:
-
DER — These file types have extensions of
.cerand.crt. There is no difference between these types. One file stores one binary certificate. -
PEM — These file types have extensions of
.pem,.txt, and.0. There is no difference between these types. One file stores one or more certificates.
You can use procertm
to convert digital certificates between .der and
.pem file formats. For more information see
Convert digital certificates in
Java Open Clients.