How to set the Session Timeout for Identity and Sysadmin Console in 11g R2 PS2

Set the Session Timeout for Identity and Sysadmin Console in 11g R2 PS2

1. Shut down all servers

2. Backup the following application EAR files 

$ORACLE_HOME/server/apps/oracle.iam.console.identity.self-service.ear

$ORACLE_HOME/server/apps/oracle.iam.console.identity.sysadmin.ear

3. Modify the following application EAR files 

$ORACLE_HOME/server/apps/oracle.iam.console.identity.self-service.ear

$ORACLE_HOME/server/apps/oracle.iam.console.identity.sysadmin.ear

4. Copy these files to a working/local machine and edit using 7zip or some other tool that deals with large ZIP files

5. Within these ear files only the web.xml needs to be modified.

Following is the full path to the web.xml files that need to change:

• oracle.iam.console.identity.self-service.ear/oracle.iam.console.identity.self-service.war/WEB-INF/web.xml

• oracle.iam.console.identity.sysadmin.ear/oracle.iam.console.identity.sysadmin.war/WEB-INF/web.xml

6. For both web.xml files, search for the session-timeout tag and place your desired value. The unit is in minutes.

Example in web.xml file

<session-config>

<session-timeout>60</session-timeout>

</session-config>

7. Start all servers

Update the LDAPRole.xml Metadata File

Update the LDAPRole.xml Metadata File in 11gR2PS2

 

Since we are referencing the CustomParentOU UDF in the LDAPContainerRules.xml file, we need to make sure that attribute is available to the process.  We do that by adding the CustomParentOU attribute to the LDAPRole.xml metadata file.

 

Add the following attribute to the <entity-attributes> section of the /metadata/iam-features-ldap-sync/LDAPRole.xml file.

 

<attribute name="CustomParentOU">

<type>string</type>

            <required>false</required>

            <MLS>false</MLS>

            <searchable>false</searchable>

            <attribute-group>Basic</attribute-group>

</attribute>

 

NOTE:  Since metadata can be updated several different ways and at different times, it is possible that this value may already exist in the LDAPRole.xml file.  If it already exists, then this step can be skipped.

 

If the file is updated and saved, then the managed OIM servers need to be restarted.