§Debugging SSL Connections
In the event that an HTTPS connection does not go through, debugging JSSE can be a hassle.
WS SSL provides configuration options that will turn on JSSE debug options defined in the Debugging Utilities and Troubleshooting Security pages.
To configure, set the
ws.ssl.debug property in
ws.ssl.debug = [ "certpath", "ocsp", # "all " # defines all of the below "ssl", "defaultctx", "handshake", "verbose", "data", "keygen", "keymanager", "pluggability", "record", "packet", "plaintext", "session", "sessioncache", "sslctx", "trustmanager" ]
NOTE: This feature changes the setting of the
java.net.debugsystem property which is global on the JVM. In addition, this feature changes static properties at runtime, and is only intended for use in development environments.
To see the behavior of WS, you can configuring the SLF4J logger for debug output:
If you are working with WSClient instances created dynamically, you can use the
SSLDebugConfig class to set up debugging using a builder pattern:
val debugConfig = SSLDebugConfig().withKeyManager.withHandshake(data = true, verbose = true)
Oracle has a number of sections on debugging JSSE issues:
Next: Loose Options
Found an error in this documentation? The source code for this page can be found here. After reading the documentation guidelines, please feel free to contribute a pull request. Have questions or advice to share? Go to our community forums to start a conversation with the community.