Upgrade an OpenEdge Authentication Gateway instance configuration
- Last Updated: January 17, 2024
- 2 minute read
- OpenEdge
- Version 12.8
- Documentation
OpenEdge Authentication Gateway instances created in OpenEdge 11.6.x or 11.7.x are not compatible with OpenEdge 12.
To upgrade your Authentication Gateway instance configuration from 11.7.x to Release 12, complete the following steps:- Back up the instance to save your 11.7.x configuration.
- Create a new Authentication Gateway server instance during the OpenEdge 12 installation process.
-
Upgrade the 11.7.x configuration from the backup to the new
Version 12 instance:
-
Configure the
HTTPSport (the procedure is unchanged from 11.7.x). -
Copy the
tomcat-keystore.p12file, which has the server instance’sTLSprivate key and server certificate, to the Version 12 instance (/oeauthserver/conf). -
Merge any
HTTPSkeystore and password configuration. - Merge any configuration changes made to the conf/openedge.properties file from the 11.7.x instance using your preferred merge tool.
- Copy the tomcat-users.xml file from the 11.7.x instance to the Version 12 instance (/oeauthserver/conf).
-
Copy any
.rABL application files from the 11.7.x instance (OERealm, Policy, and Event handlers) to the Version 12 instance. -
Copy the OpenEdge domains configuration file (
domains.json) from the 11.7.x instance to the Version 12 instance (/oeauthserver/webapps/ROOT/WEB-INF/configdirectory). -
Copy the users.properties file from the 11.7.x instance to the
Version 12 instance (
/oeauthserver/webapps/ROOT/WEB-INF/configdirectory). -
Create a new domain registry keystore file (
domains.keystore) from the 11.7.x instance’sdomainsks.csvfile using thegendomregutility, and add the newdomains.keystorefile to the /oeauthserver/webapps/ROOT/WEB-INF/config directory in the Version 12 instance. -
Merge the 11.7.x instance
sts.propertiesconfiguration file with the Version 12 instancests.propertiesfile using your preferred merge tool.
-
Configure the
-
If you have Security Token Service (STS) key security enabled
for your 11.7.x instance, then:
-
Create a new Version 12 STS server key file using the
same
-urlparameter as was used to generate the 11.7.x server-key file. Store the new STS server key file in the location that is specified as the value of thests.server.keyfileproperty in thests.propertiesfile. -
Install a new STS client key file on the local server
using the
stskeyutiltool. -
Test the STS server key access using the
stskeyutiltool.
-
Create a new Version 12 STS server key file using the
same
-
Start the Version 12 instance, and then test access to the
instance OpenEdge domain configurations using the
stsclientutiltool. -
If you have enabled STS key security for your Authentication
Gateway, then:
- Install a new STS client key in all OpenEdge 12 client installations that replaced the 11.7.x installations.
-
Test the client key access using the
stsclientutiltool.
- Test the Version 12 PAS for OpenEdge and OpenEdge database connections that are configured to use the Authentication Gateway.