auth.user.prevent-concurrent-user-login-sessions

Background

Set whether users of Funnelback should be prevented from logging in simultaneously from multiple web browsers. Note that this restriction does not apply to Funnelback service users which always need the possibility of multiple sessions (e.g. one per currently running collection update).

Normally it is helpful for users to be able to log on to Funnelback’s administration interface from multiple browsers or multiple locations, however this is sometimes seen as a security risk, so this option provides the ability to invalidate all previous user sessions as soon as a new one is created.

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.prevent-concurrent-user-login-sessions key, and set the value. This can be set to any valid Boolean value.

Default value

Multiple concurrent sessions are permitted by default

auth.user.prevent-concurrent-user-login-sessions=false

Examples

Prevent concurrent sessions by setting the value to true.

auth.user.prevent-concurrent-user-login-sessions=true