Test SAML configurations
- Last Updated: August 12, 2026
- 2 minute read
- OpenEdge
- Version 13.1
- Documentation
System Administrators use OESECTOOL to test SAML configurations for PAS for OpenEdge and OpenEdge Authentication Gateway security configurations. Testing is limited to checking for valid or invalid responses. Testing does not provide user login and session support.
Syntax
|
Parameters
- command
- The commands related to SAML testing, including:
| Command | Description |
|---|---|
| startsamlserver | Starts a SAML identity provider.
Note: Using -port or -ports creates
a keystore.p12 file in
oesectool/work, if not already present.
Using -ports also creates an
sslkeystore.p12 file in
oesectool/work, if not already present.
In addition, starting the server generates
oesectool/work/oesectool.0, a PEM file
containing the server certificate. If your PAS for OpenEdge
instance uses the OS Trust Store, add this certificate to the OS
Trust Store before running tests. See OESECTOOL utilities. |
| stopsamlserver | Stops a SAML identity
provider.Note: You can stop the server from the browser by
using http://machinename:port/stop or
https://machinename:ports/stop. |
parameters- The parameters related to SAML testing, including:
| Parameter | Description |
|---|---|
| -port portnumber | HTTP port number |
| -ports portnumber | HTTPS port number |
Customize SAML server properties
When you use OESECTOOL to start a SAML test server, modify theoesectool/conf/oesectool-saml.properties file to configure a SAML test server. For more information on oesectool-saml.properties, see the oesectool/conf/oesectool-saml.properties.README file.
Start a SAML test server
|
|
When the SAML server starts, it creates two keystore files in your work directory:
-
keystore.p12—Keystore to sign tokens. This keystore has only one key
defsigkeyand a self-signed certificate for testing. A unique keystore is created on initial startup in oesectool\work when an HTTP port is provided. -
sslkeystore.p12 —Keystore for HTTPS requests. This keystore has the
oesectoolsslkey and a self-signed certificate for testing. To send HTTPS requests, PAS for OpenEdge must have theoesectoolsslcertificate in the Tomcat truststore or reassign the Tomcat truststore to sslkeystore.p12. A unique keystore is created on initial startup in oesectool\work when an HTTPS port is provided.
Customize the keystore location and password
OESCTOOL catalina_opts template command before starting a test PAS
for OpenEdge instance. This command sets the Tomcat truststore of the instance to
the truststore created for OESECTOOL, when using HTTPS. - Windows:
oesectool.bat catalina_opts set CATALINA_OPTS=-Djavax.net.ssl.trustStore="C:\workdir\sslkeystore.p12" -Djavax.net.ssl.trustStorePassword=yourpassword - Linux or Unix:
sh oesectool.sh catalina_opts export 'CATALINA_OPTS=-Djavax.net.ssl.trustStore=/workdir/sslkeystore.p12 -Djavax.net.ssl.trustStorePassword=yourpassword'
Set up the OS Trust Store for OESECTOOL testing
If your PAS for OpenEdge instance is configured to use the OS Trust Store, complete the following steps before running SAML tests. This setup is required only once per server.
- Start the OESECTOOL SAML server using the
-portsparameter to ensure the server certificate is generated:
OESECTOOL creates work/oesectool.0 containing the generated server certificate.oesectool startoauth2server -ports portnumber - Stop the server:
oesectool stopoauth2server -ports portnumber - Add the generated certificate to the OS Trust Store:
- On Linux: run install_certificates.sh.
- On Windows: run import-certificates.bat.
gencert command to generate
work/oesectool.0 without starting a server, then add the
certificate to the OS Trust Store. For more information, see
OESECTOOL utilities.Stop a SAML test server
|