Environment:
Oracle Access Manager (OAM) 14c 14.1.2.1
Issue:
When testing an application like Oracle Forms and Reports secured with OAM, session lifetime doesn't work when the configured value is greater than 480 minutes/8 hours.
User is asked to login again after 8 hours.
How to fix the issue:
You have to export the OAM configuration from the database to a file, then change the "" parameter and set the desired value.
Finnally import the OAM configuration back to database, this process will automatically update the oam config file from the domain.
Example:
1. Create prop.properties file:
You will set here the connection values to connecto to OAM repository:
oam.entityStore.ConnectString=jdbc:oracle:thin:@oamdb-scan:1521/OAMDB
oam.entityStore.schemaUser=DEV_OAM
oam.entityStore.schemaPassword=pass_oam_repo
oam.importExportDirPath=/home/oracle/oamconfig
oam.frontending=params=host;port;protocol
2. Export OAM configuration:
Run the following command:
java -cp $ORACLE_HOME/idm/oam/server/tools/config-utility/config-utility.jar:$ORACLE_HOME/oracle_common/modules/oracle.jdbc/ojdbc11.jar oracle.security.am.migrate.main.ConfigCommand $DOMAIN_HOME export /home/oracle/oamconfig/prop.properties
3. Change "CredentialValidityInterval" parameter to disered value:
Look inside oam-config.xml file for the parameter and change the value in minutes:
In my case 840 Minutes = 14 Hours
4. Import OAM configuraton back again to database:
Now, the final step is to import back the modified xml to database. Run the following command:
java -cp $ORACLE_HOME/idm/oam/server/tools/config-utility/config-utility.jar:$ORACLE_HOME/oracle_common/modules/oracle.jdbc/ojdbc11.jar oracle.security.am.migrate.main.ConfigCommand $DOMAIN_HOME import /home/oracle/oamconfig/prop.properties
Best regards
Carlos Cortez