We have a timeout of 30 min for our fiori launchpad and is working fine. So if a user is inactive for 30 min, user session is being killed in SM05. Now, if user clicks on any tile on launchpad browser is giving a pop up to enter user credentials.
If user provides his credentials in the pop up, browser is remembering(cache) those details. So after next 30 min, again the session being timed out and session is being killed in SM05. But if user clicks on any tile now, a new session for the user is automatically created as the browser has already remembered his credentials.
I couldn't find any way to restrict browser from caching the authentication details. Is there any way where we can configure the caching time of browser authentication details? Or is there any way I can show login page to the user instead of allowing him to click on launchpad after the timeout?
We are using basic authentication for our fiori applications and do not have a web dispatcher.
Thanks,
Avinash
2 Answers
-
Feb 28, 2018 at 09:46 PM
If you are using SSO as suggested with SAP Fiori, the login cookie timeout I believe defaults to 8 hours. You can set parameter 'login/ticket_expiration_time' by Tcode <RZ11> which controls the expiration time of SSO ticket. This may be your issue.
-kevin
Add comment
-
Mar 01, 2018 at 10:08 PM
You can see if you can deactivate logon ticket caching, login/ticketcache_off=1.
Add comment
Add comment