OESECTOOL
- Last Updated: August 12, 2026
- 2 minute read
- OpenEdge
- Version 13.1
- Documentation
- Test OAuth2 configurations with PAS for OpenEdge and OpenEdge Authentication Gateway.
- Test SAML configurations with PAS for OpenEdge and OpenEdge Authentication Gateway.
Syntax
|
Logging
OESECTOOL generates a log file oesectool.year-month-day.log in the oesectool/work directory. To change the logging configuration settings, modify the logging-oesectool.xml file located in the oesectool/conf directory.
Certificates
OESECTOOL uses a consistent private key and certificate generation process that supports environments where certificate validation is managed outside of a Java trust store.
In previous releases, OESECTOOL generated a new private key and self-signed certificate each time it started a test server. Because the certificate changed for every test run, administrators had to repeatedly update trusted certificates, making the tool difficult to use in environments that depend on operating system certificate stores.
Starting in OpenEdge 13.1, OESECTOOL uses the bundled
conf/oesectool.pem file as the source of its private key. As a
result, certificates generated by OESECTOOL are based on the same key pair for a
given server and can be trusted once and reused across multiple test sessions. The
generated certificate is written to work/oesectool.0.
For more information, see Manage certificate stores for OpenEdge clients and servers.