Encrypt payloads
- Last Updated: January 26, 2026
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
- Create a keystore containing a public and private key pair.
- Provide the public key certificate to the authentication server to encrypt the message.
- Configure PAS for OpenEdge to locate the private key to decrypt the message.
For more information on asymmetric public key encryption, see Asymmetric public key cryptography.
Create a keystore containing a public and private key pair
This example uses the default keystore included with PAS for OpenEdge. Production systems must generate a secure keystore based on your company-specific certificates.
For more general information on creating a keystore, see Use the keytool utility
Provide the public key certificate to the authentication provider to encrypt the message
-
Provide the URL of the keystore to the authentication server
-
Use the tools of the authentication server to locate public key certificate
Provide the URL of the keystore to the authentication server
You can share a URL to the keystore containing the public key certificate for development and test systems. Configure PAS for OpenEdge to share the default URL:
publicKeys.keystore.path=${catalina.base}/ablapps/${oeabl.ablapp.name}/conf/${oeabl.ablapp.name}.p12
publicKeys.keystore.pwd=oeph0::76E5F6C162276768465F02E4D2D1DDCD
publicKeys.keystore.aliases=defaultkey
publicKeys.filter.url=/oauth2/keys
The authorization server uses the URL to get the keys.
http://hostname:port/oauth2/keys- Export the key certificate using the KEYTOOL
utility.
proenv>keytool -exportcert -keystore C:\OpenEdge\WRK\oepas1\ablapps\oepas1\conf\oepas1.p12 -storepass password -alias defaultkey -file myCertificate.crtNote: This example uses the default keystore, alias, and password. - Locate the certificate using the API, user interface, or tools of the authentication server.
Configure PAS for OpenEdge to locate the private key to decrypt the message
To decrypt the payload, configure PAS for OpenEdge to use the appropriate keystore containing the private key by configure the following:- Set the related JWE properties in the relevant
oeablSecurity.propertiesfile.## "jwe": JWT Encryption jwtToken.keystore.jwe.key.selector=pkcs12EncKeySelector jwtToken.keystore.jwe.path=keystorePath jwtToken.keystore.jwe.pwd=keystorePassword jwtToken.keystore.jwe.alias=keystoreAlias jwtToken.keystore.jwe.cache=trueNote: ThekeystorePath,keystorePassword, andkeystoreAliasare unique to your system.Table 1. JWE properties Property Description jwtToken.keystore.jwe.key.selectorIdentifies the key selector. The valid values are: noJWEKeySelectorpkcs12EncKeySelector
jwtToken.keystore.jwe.pathPath to the local key store with private keys. The default value is [ ]. jwtToken.keystore.jwe.pwdEncrypted keystore password similar to jwtToken.keystore.pwdto access the keystore store defined byjwtToken.keystore.jwe.path. The default value is [ ].jwtToken.keystore.jwe.aliasList of private key aliases in the JWE keystore. The default value is [ ]. jwtToken.keystore.jwe.cacheDefines whether to cache JWE private keys or extract them from the keystore every time. The default value is true.Note: This example uses apkcs12EncKeySelectoravailable with PingFederate. - Save the file.