No data loss after a session transaction

The Oracle Central Coding application is configured to require users to re-enter their user names and passwords after a defined period of inactivity. The user can log in and continue working without losing data.

In environments with native authentication, this security feature is controlled by the following settings on the System Configuration page:

• Authentication inactivity timeout—Period of inactivity after which a user session times out. Default is 20 minutes.
• Authentication expiration—Length of time after which a user session times out. Default is 4 hours (240 minutes).
• Authentication token duration—Length of time the user login is valid. Default is 10 hours.
• Authentication token renew duration—Length of time a previously created security token can be renewed without requiring a user to re-enter the user name and password. Default is one week.
• Authentication token clock slush—Number of minutes the server clocks for the Oracle Central Coding and Oracle InForm Adapter application servers can be out of sync. The default is 5 minutes (meaning that a token will be accepted if the server clock is within 5 minutes of the server that issued the token).