Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 212 Oracle Analytics News
- 42 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 78 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
User is logged out of the system even though user is working in the system actively after a time of
Organization Name
Corporativo Bimbo S A De C V
Description
User is logged out of the system even though user is working in the system actively after a time of 8Hrs
We received the response from the SR for this issue that
Standard values for timeouts are as documented in Cloud Service guide (pre-Release 13).
8 hrs token validity
1 hr inactivity timeout
30 min idle session timeout
For your release 13 environment.
Currently non-configurable.
Current configuration settings are:
Current Idle session timed out value is 120 mins (obtained from web.xml)
Session Lifetime value is 480 mins.
Use Case and Business Need
But the users are not satisfied on this system behaviour. Atleast the user needs some alert/notification before it kicks them out of the tool to the login page after 8 hrs of work so that user can save the process they were working.
It will be more useful if we can alter these session timeout lifetime on site level in the system as a custom configuration.
Original Idea Number: 8634c625b1
Comments
-
Our users are running analytics and because they are SO SLOW they are moving on to other tasks, and coming back to the data after 10minutes. Only to find out they are now timed out. It's extremely frustrating.
0 -
This happens quite often for our users as well, even in the middle of actively editing a workbook. Being able to modify the timeouts would be great.
0 -
@bbci_BeverlyBaker -- this is something worth investigating. Often slow queries are due to database or data model design. It is usually possible to have fast queries.
@andrefecteau -- in DV workbooks and datasets at least -- the user should be prompted to re-authenticate without losing their work. This was added last year. Is this not working correctly for your users?
0 -
@Bret Grinslade - Oracle Analytics-Oracle - absolutely agree but in the cloud we have no control over the poor design of the abstraction layer and/or the db iteslf. My experience is painful regarding performance and cloud OTBI. Regardless we also time out during active development and adhoc queries. We are not prompted to reconnect. this is a massive issue for my client.
0 -
@Bret Grinslade - Oracle Analytics-Oracle it is working correctly for our users, but it's still jarring when they are actively using OAC and then it prompts them to re-login.
0 -
To solve this problem (timeout) we need a parameter, at user level, to be able to modify this value in Fusion (for example to increase it from 8 to 12 hours).
0
