Categories
how to extend the application timeout?
Sometimes I can't save the reports I have been building because the application closes the session, supposedly because of “timeout”, but even being connected and working 100% the application closes.
Why this behavior? is there a way to extend or remove the "timeout" in OAC?
Answers
-
@SERGIO BARRETO - Session timeouts is managed by the identify management system not specific services. In IDCS/IAM there is a way to setup timeout policies. Both offer settings for session timeouts (inactive) and session duration (active).
Kindly refer the below document for steps:
1 -
Hi @SERGIO BARRETO ,
This may be an IDCS "Session Duration" setting.
Per DocID: 3008618.1
User Timeouts are controlled by IDCS when IDCS is the only identity provider.
To change this for a user from the FAW Console goto Security > Users > Manage Users.
Then under "Identity domain" on the left select: Settings > Session settings.
Here you can change the Session Limits.
The defaults are:
Session duration (in minutes): 600
The duration that you want the session to remain active after the user signs in. Valid values are between 1 and 32,767.
My Apps idle timeout (in minutes): 480
The
duration after which a user is automatically signed out of the My Apps
console of this identity domain due to inactivity. Valid values are
between 5 and 480. To set the OCI Console timeout, open the Profile menu
(User menu icon) and then click Console Settings.*Note: If there are any other IDPs in the environment it will take the shortest session timeont.
Regards,
John
1 -
The session timeout for both FAW and OAC is managed through the IDCS admin console. By default, the timeout is set to 480 minutes. This setting can be modified through the SAML (SSO) configuration you're using, but any changes to the timeout will need to be coordinated with your SAML provider.
Please note that the timeout settings are not maintained within FAW or OAC directly. There is an ongoing discussion about this on IdeaLab, which you can follow here:FAW Idle Timeout Discussion
For further reference, you can review the following resources:
- Note 2355025.1: OCI Identity Cloud Service (IDCS) – Is the IDCS Session Settings, 'Session Expiry', based on user activity?
- Changing IDCS Session Settings
1 -
Thank you all for your response.
@RanaAshutosh-Oracle the post you share is just like my situation, the 480 minutes in IDCS is fine, but still after 45 0 60 minutes the application shuts down, even when I am working on creating a report or workbook.
I was even looking at some system options from FDI, and I have the following settings:
change the option: “User Inactivity Timeout (minutes)”. from 60 to 480 would it work? would this change apply to all users?
0 -
@SERGIO BARRETO This is to specifies the number of minutes users are inactive before their browser or mobile connection must be re-authenticated. You can test it. Refer : How to set User Inactivity Timeout for Oracle Analytics Cloud? (Doc ID 2980320.1)
0 -
@SERGIO BARRETO In case your user is federated (SSO configured user) then the session timeout would need to setup at the Fusion SSO's IDP.
0
