Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.8K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
OAM 12c Session lifetime and Idle session timeout

Hi,
We are currently on OAM 12.2.1.3
I have few queries regarding Max sessions per user, Session lifetime and Idle session timeout settings in the OAM Common settings page.
We use OAM as an IdP and use SAML federation. Our current settings are
Max sessions per user =10
Session lifetime=720 minutes
Idle session timeout=720 minutes
Now, few of the users are reaching max session count of 20 and not able to login/create any new sessions.
Questions :
1) How the max sessions get reached, if the user tries to access the different applications in a SSO environment ?
-- if i open app1--> browser window1, app2-->browser window2, app3 -->browser window3; does this count as 3 sessions for the user or only 1 as it's a SSO for all the 3 apps.
2) If the user closes the browser, does the session gets killed ?
3) If the user opens a new browser immediately after closing the browser, does a new session get created ?
4) Is there something that i have to educate/tell users going forward so that max session scenario doesn’t happen again?
5) In a federated login, can we get details of what Service provider or URL the user has tried to access ?
6) If we don't delete the sessions from OAM, when will the 10 sessions get expired so that the user can log in again ?
Any inputs would be appreciated on this .
Any other scenarios/questions that you have faced would be helpful for me to educate users and also answer questions raised by management.
Thanks in advance.
Best Answer
-
Yes try to decrease the Session Lifetime which is currently set to 720 minutes- as per your post. Set this Session Lifetime to 240 or 300 minutes which is 5 hours. Or set to a lower value if that works at your project... If your project allows then try to set it for 120 minutes which is 2 hours. Hopefully this will help resolve your issue.
Answers
-
Hi,
Any inputs on this please?
Thanks in advance
-
-
Hello,
Please refer to this blog for details on session timeout for OAM. Also can you let us know or confirm if OAM is protecting access to the Application? You mentioned OAM is IDP and using saml federation. In Federation there are two end points, one is Identity Provider and the other is Service Provider.
The blog reference is for setting up OAM as service provider for application. I will try to answer you current questions assuming OAM is configured to protect the access to the application/Application URL.
>>1) How the max sessions get reached, if the user tries to access the different applications in a SSO environment ?
-- if i open app1--> browser window1, app2-->browser window2, app3 -->browser window3; does this count as 3 sessions for the user or only 1 as it's a SSO for all the 3 apps.
Above will count as 3 sessions. But be aware if you open multiple tabs in the same browser then you are sharing the same cookie. To avoid confusion open one session in one browser, say IE, then open another session in a different browser, say Chrome browser.
>>2) If the user closes the browser, does the session gets killed ?
Yes
>>3) If the user opens a new browser immediately after closing the browser, does a new session get created ?
Yes
>>4) Is there something that i have to educate/tell users going forward so that max session scenario doesn’t happen again?
There is a setting for Max user sessions in OAM configuration. By default believe it is set to 8. Here is a reference regarding maximum sessions. (Scroll down to section 25.3.1.3.1 Global Session Settings and see the info on Maximum Number of Sessions) Note if you set this value to 0 (zero) then that is a special setting, and this will ensure that OAM will count the sessions of a user thereby a user can have unlimited number of sessions- obviously this setting of zero (0) is not to be used.
>>5) In a federated login, can we get details of what Service provider or URL the user has tried to access ?
Yes as an admin you should have this information. If not contact the Service Provider admin. If you are in a Federation then you -I am assuming as an administrator should have access to details both at IDP and SP side (Identity Provider and Service Provider). Looks like you are from the Identity Provider side?
>>6) If we don't delete the sessions from OAM, when will the 10 sessions get expired so that the user can log in again ?
The sessions will get expired when the "Session Lifetime is reached the session is marked as expired and removed from server memory. Again you can read here about Session Lifetime.
Just to be clear here the settings for OAM that is being discussed is assuming OAM is protecting the application/URL or in other words it is the Service Provider. So I am assuming your Service Provider is also running OAM? please confirm.
-
Thank you @Sandeep Kumar sk for taking time and reply to the post. Appreciate it.
We are using OAM as an Identity Provider and application ( ex. Workday) as the Service Provider. This is a SAML 2.0 based SSO. Our current Global Settings from OAM page are :
Max sessions per user =10
Session lifetime=720 minutes
Idle session timeout=720 minutes
Few of the users are getting maxed out of 'Max Sessions per user'=10 and asking us to what we need to do going forward so that max session scenario doesn’t happen to them again?
From database, i am able to see the sessions of the user's in 'AM_SESSION' table ( like client ip, userid etc.,) but not the url what they accessed. is there a way to find out.
Thanks in advance.
-
You can increase this current setting of Max sessions per user =10 to say 30
Check with your users if this helps. For the URL, you can always check the Federation configuration settings which will give the URL.
-
Recently we increased it to 20 and as per Oracle increasing it to higher value will have database performance issues and other security issues.
Still few of the users are getting maxed out of user sessions and we need to clear the sessions in backed from AM_SESSIONS table. Can we decrease the Idle session timeout so that the session gets timeout sooner and the user will have sessions to consume. Any suggestions.
For the URL, you can always check the Federation configuration settings which will give the URL.
I know the SP URL. But, wanted to know from the number of sessions the user has, what is it they are accessing ?
Thanks,
-
Yes try to decrease the Session Lifetime which is currently set to 720 minutes- as per your post. Set this Session Lifetime to 240 or 300 minutes which is 5 hours. Or set to a lower value if that works at your project... If your project allows then try to set it for 120 minutes which is 2 hours. Hopefully this will help resolve your issue.
-
@user8744020 can you confirm if the setting of session timeout resolved your issue?
-
Yes, the information was very helpful. I wanted to mark this discussion as answered but i don't see 'Answered' button. I only see below options.
Thanks,
-
@user8744020 you should be able to do now...