You can update your session expiration time by increasing this variable in config file: $config[‘sess_expiration’] = ‘somevalue’. Set $config[‘sess_expiration’] = 0, if you want it to never expire. Here’s a good discussion on CI forums: Dynamically set configuration on session expire doesn’t work
I’ve got a simpler solution. This works for both logout and session timeout. @Component public class LogoutListener implements ApplicationListener<SessionDestroyedEvent> { @Override public void onApplicationEvent(SessionDestroyedEvent event) { List<SecurityContext> lstSecurityContext = event.getSecurityContexts(); UserDetails ud; for (SecurityContext securityContext : lstSecurityContext) { ud = (UserDetails) securityContext.getAuthentication().getPrincipal(); // … } } } web.xml: <listener> <listener-class>org.springframework.security.web.session.HttpSessionEventPublisher</listener-class> </listener>
They are not the same. The IIS session timeout is for clasic ASP pages. The web.config one is for asp.net.
Try ng-idle. It’s simple component where you can set the timeout and warning time before the timeout is reached. Then you can query server for user logout or something similar. myApp.config(function(IdleProvider, KeepaliveProvider) { IdleProvider.idle(900); // 15 min IdleProvider.timeout(60); KeepaliveProvider.interval(600); // heartbeat every 10 min KeepaliveProvider.http(‘/api/heartbeat’); // URL that makes sure session is alive }); myApp.run(function($rootScope, … Read more
Exceptions which are thrown during ajax requests have by default totally no feedback in the client side. Only when you run Mojarra with project stage set to Development and use <f:ajax>, then you will get a bare JavaScript alert with the exception type and message. But other than that, and in PrimeFaces, there’s by default … Read more
To handle the exception whenever the user invokes a synchronous POST request on a page while the HTTP session has been expired and the JSF view state saving method is set to server, add an <error-page> to the web.xml which catches the JSF ViewExpiredException and shows the home page. <error-page> <exception-type>javax.faces.application.ViewExpiredException</exception-type> <location>/home.xhtml</location> </error-page> To handle … Read more
You can either set the session timeout (say 60 minutes) for all sessions in web.xml: <session-config> <session-timeout>60</session-timeout> </session-config> or on a per-session basis using session.setMaxInactiveInterval(60*60); the latter you might want to do in a authorizationSuccessHandler. <form-login authentication-success-handler-ref=”authenticationSuccessHandler”/>
Another option would be modifying web.xml. Prior you must call grails install-templates Then edit src/templates/war/web.xml and add/modify after servlet-mapping: <session-config> <session-timeout>60</session-timeout> </session-config> The value of session-timeout uses minutes as unit.
Now, i’m being told that this will terminate the session (or is it all sessions?) in the 15th minute of use, regardless their activity. This is wrong. It will just kill the session when the associated client (webbrowser) has not accessed the website for more than 15 minutes. The activity certainly counts, exactly as you … Read more