Try OpenEdge Now
skip to main content
Installation and Configuration
Command and Utility Reference : Installing and managing keys and digital certificates : sslj : s_client
 
s_client
Starts the HTTPS client with the parameters provided.
Operating system
Syntax
UNIX
Windows
sslj s_client -connect host:port
-CAfile CA file path-CAPass CA password
[-cert certificate path][-certPass certificate password]
[-protocol][-debug debug value]
[-log log directory path]
-connect host:port
Provides the host and port name that the client uses to connect to the server.
-CAfile CA file path
Provides the path for the CA certificate for server authentication.
Note: The supported file extensions for the certificate are .jks and .p12. Make sure that you provide the absolute path, for example, C:\xyz\abc.p12.
-CAPass CA password
Provides the password for the CA certificate.
-cert certificate path
Provides the path where the server certificate for client authentication resides.
Note: The supported file extensions for the certificate are .jks, .jceks, .p12, .pfx, .bks.
-certPass certificate password
Provides the password for the server certificate.
-protocol
Specifies the protocol that the client uses.
-debug debug value
Turns on the debugging, the valid values are all and ssl. Here are the values that you can choose for ssl:
*record: Enables tracing for each record. The valid values are plaintext for hex dump of record and packet for raw SSL or TLS packets.
*handshake: Displays each handshake message. The valid values are data for hex dump of each handshake message and verbose for handshake message printing.
*keygen: Displays the key generation data.
*session: Displays the details of the session activity.
*defaultctx: Displays the default SSL initialization.
*sslctx: Displays the SSL context tracing.
*sessioncache: Displays the session cache tracing.
*keymanager: Displays the key manager tracing.
*trustmanager: Displays the trust manager tracing.
Note: If you have provided a filename using the -log option, the above details are updated in the file or else, they are displayed on the proenv.
-log log directory path
Specifies the path where the s_client.log file is generated.
Examples:
proenv>sslj s_client -connect localhost:8888 -CAfile ca.p12 -CAPass password
-cert server.p12 -certPass password -debug ssl:session -log C:\Progress\WRK -TLSv1.1
proenv>sslj s_client -connect localhost:8888 -CAfile ca.jks -CAPass password
-cert server.jks -certPass password -debug ssl -log C:\Progress\WRK -TLSv1.1
Note: For more information on an example on creating and managing a .jks keystore, see the OpenEdge Management and OpenEdge Explorer: Getting Started guide.