View Issue Details

IDProjectCategoryView StatusLast Update
0001048savapage-server[All Projects] Generalpublic2019-08-05 16:41
ReporterrijkrAssigned Torijkr 
Status closedResolutionfixed 
Product Version1.0.0 
Target Version1.1.0Fixed in Version1.1.0 
Summary0001048: Improve use of max inactive session interval
DescriptionIST: When web-login.authtoken.enable == Y, MaxInactiveInterval of HTTP session is set to zero (0). An interval value of zero or less indicates that the session will never expire. If the user logs out properly by pushing the Logout button, the session is removed by SavaPage server. However, if the user closes the browser (tab) without explicitly logging out of teh Web App, the session will not be removed ever.

SOLL-1: Ignore web-login.authtoken.enable, and always use MaxInactiveInterval with value of "web-login.user.session-timeout-mins" or "web-login.admin.session-timeout-mins". As these *-timeout-mins items have default values GT zero (0), a user will encounter a "Your session has expired" message in the Web App, if he acts after *-timeout-mins inactivity. But, if web-login.authtoken.enable == Y, a press on the Continue button open the Web App again without the need to logon. If user closes the browser (tab) without explicitly logging out, the session will be marked for removal after *-timeout-mins. The actual removal is performed during the next session scavenge cycle. See "server.session.scavenge.interval-sec" key in

SOLL-2: Admin Web App > Dashboard shows the number of Client sessions (User Web App and User Client).

SOLL-3: Admin Web App > Dashboard shows the number of cached HTTP sessions id's and corresponding client ip addresses. Due to DHCP, the number of ip's may be greater then number of id's. See 0001047
TagsNo tags attached.


related to 0001047 closedrijkr Prune orphaned IP addresses from session cache 



2019-08-05 16:41

administrator   ~0000151

release 1.1.0

Issue History

Date Modified Username Field Change
2019-04-01 20:33 rijkr New Issue
2019-04-01 20:33 rijkr Status new => assigned
2019-04-01 20:33 rijkr Assigned To => rijkr
2019-04-01 20:33 rijkr Relationship added related to 0001047
2019-04-02 20:41 rijkr Status assigned => resolved
2019-04-02 20:41 rijkr Resolution open => fixed
2019-04-02 20:41 rijkr Fixed in Version => 1.1.0
2019-08-05 16:41 rijkr Status resolved => closed
2019-08-05 16:41 rijkr Note Added: 0000151