Set how long, as a percentage of the user’s login token lifetime, should pass before the user’s login token should be refreshed on the next request.

For example, if this value is set to 20 (i.e. 20%) and the token lifetime is set to 10 hours (i.e. 36000 seconds) then the user’s token would be unchanged for the first two hours of usage and would then be refreshed (i.e. the user would be given a brand new 10 hour token) on the next request made 2 hours after their initial login.

Note that this value is read only when Funnelback’s web server is started. After modifying the value, the web server must be restarted for the change to take effect.

Setting the key

Set this configuration key in the server configuration.

Use the configuration key editor to add or edit the auth.user.login-token-refresh-after-percentage key, and set the value. This can be set to any valid Double value.

Default value

Refresh the user’s session after 20% of the lifetime has been used.



Refresh the user’s session after 5.2% of the lifetime has been used.

In practice this means sessions will be refreshed more frequently (the Funnelback server must perform more work) but the user’s session is less likely to expire unexpectedly.