1. Using Integrations in Oracle Integration 3
  2. Manage Integrations
  3. Set the Inactive Session Timeout Limit and Audit Logging Levels

Set the Inactive Session Timeout Limit and Audit Logging Levels

You can set the time limit for inactive sessions in an Oracle Integration instance. This setting automatically signs out a currently authenticated user after a specified period of inactivity. This setting impacts all users of the instance and takes effect after a user signs out and signs back in. You can also select to capture lifestyle and observability actions in the audit logs.

Note the following guidelines for using the options on this page:
To Set the Timeout for Inactive Sessions To Set the Audit Levels
  • Only a user with the ServiceAdministrator role can view the Security page and set the time limit for an inactive session in an Oracle Integration instance.
  • The default value for an inactive session in an instance is 60 minutes, unless a user with the ServiceAdministrator role sets it to another value.
  • The minimum and maximum values for session inactivity timeouts are 15 minutes and 60 minutes, respectively.
  • Assume you have multiple open tabs in your browser for the same integration instance.
    • You are actively working in one tab.
    • The other tab remains idle.
    When the session inactivity timeout value for the integration instance is reached for the idle tab, you are not logged out of either tab.
  • Assume user A is signed in when the session inactivity timeout is set to 45 minutes. A user with the ServiceAdministrator role then changes the setting to 30 minutes. The previous setting of 45 minutes remains in effect for user A as long as they are signed in. Once they sign out and sign back in, the setting of 30 minutes takes effect.
  • Only a user with the ServiceAdministrator role can activate or deactivate observability auditing. This change is always logged to the lifecycle audit log.
  1. In the navigation pane, click Settings, then Security.

    The Idle session timeout section shows the Session times out after 15 minutes slider. The slider shows a maximum value of 60 seconds. The Audit level section shows options for Lifecycle actions only and Lifecycle actions and observability, which includes a suboption for Log user searches.

  2. To set the timeout limit for inactive sessions:
    1. Drag the slider to the applicable session inactivity value.
    2. Click Save.
    3. If you want to revert to the previous session inactivity value, click Revert.
  3. To set the audit level for lifecycle actions and observability.
    1. Select the level of auditing to perform.
      Element Description
      Lifecycle actions only Logs lifecycle actions to the audit logs. This option is enabled by default. Lifecyle actions include the following:
      • Integration activation and deactivation
      • Connection creation, deletion, and update
      • Integration unlocking, importing, and exporting
      Lifecycle actions and observability Select to log both lifecycle actions and observability details to the audit logs (such as runtime messages). The observability audit captures the following actions:
      • Changing the tracing level of an integration.
      • Accessing any Observability page or API that displays business identifiers or any payload data, specifically:
        • Viewing errors by selecting Observability, and then Errors.
        • Accessing instances by selecting Observability, and then Instances.
        • Accessing the activity stream by selecting Observability, and then Instances. This is an additional audit event on top of accessing the Instances page that logs the specific integration that was viewed.
        • B2B tracking.
      • Viewing or downloading logs from the activity stream.
      • Viewing or downloading audit logs that contain any payload data or business identifier.

      Selecting Lifecycle actions and observability enables the following option to be displayed:

      • Log user searches: Select to log the search text you entered.

        For example, if you go to the Instances page under Observability, then enter OrderOpportunity as the text for which to search, the audit log captures the text OrderOpportunity.

        If Log user searches is not selected, the audit log records that a search was conducted, but does not record the actual text that was entered.

      See Check the Audit History for an Integration or Other Component.

    2. Click Save.
    3. If you want to revert to the previous audit level values, click Revert.