Kbase P121819: How to enable SSL debugging in Progress?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/11/2009 |
|
Status: Verified
GOAL:
How to enable SSL debugging in Progress?
GOAL:
How to enable SSL debugging in WebSpeed?
GOAL:
SSL Trouble Shooting
GOAL:
How to generate debug log files for SSL?
GOAL:
How to get more debug information for Progress SSL connections?
GOAL:
How to enable debug logging for SSL client/server connections.
GOAL:
Can debugging information be gathered from SSL connections between client and server?
GOAL:
Is there a way to obtain debug information for SSL connections?
FACT(s) (Environment):
OpenEdge Category: Language (4GL/ABL)
OpenEdge 10.x
All Supported Operating Systems
FIX:
To turn on SSL debug logging, the SSLSYS_DEBUG_LOGGING environment variable must be set. Once SSLSYS_DEBUG_LOGGING is set to a value of 1 to 5, an SSL debug log file (cert.server.log for server and cert.client.log for client) will be generated in working directory ($WRKDIR) when a connection is established (using the CONNECT() method for example). If WRKDIR can not be determined, the log file will be written to /tmp directory on UNIX and C:\TMP on windows. Make sure you create a C:\TMP directory on windows for this to work.
UNIX:
SSLSYS_DEBUG_LOGGING=x;export SSLSYS_DEBUG_LOGGING
Windows:
set SSLSYS_DEBUG_LOGGING=x
The value for "x" is set from 1 to 5 depending on the level of logging required (see Note below for more information on logging level settings).
For WebSpeed, the environment variable should be set at the Environment section of the corresponding broker and the server log file will contain additional SSL debugging information.
To enable logging SSL messages in the AppServer set brkrLoggingLevel to 4 or greater within the ubroker.properties file.
Add the following to the brkrLogEntryTypes (the comma is necessary), Ubroker.SSL