Graylog2 / Graylog2/graylog2-server

Session does not get updated when changing timeout setting of a user

Open
#12,312 3 comments 0 reactions 0 assignees View on GitHub
bug test-day triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

## Expected Behavior
If I change the timeout setting of a user the current session of a user should get either updated or invalidated.
If a admin is changing the setting from "Does not timeout" to "8 hours" the admin needs to trust the user that he is
logging out so he gets a new session with a new timeout.

## Current Behavior
After changing the timeout setting from e.g 1 hour to 1 minute the session is still active for 1 hour.

## Possible Solution
Either update or invalidate the current user session so he either gets a new session with updated timeout
or he needs to login anew to get a new session.

## Steps to Reproduce (for bugs)
1. Log in as a admin user (not admin himself)
2. Change your setting from anything bigger than 1 minute to 1 minute
3. Wait for 1 minute
4. Test if you are still logged in.

## Context
If a admin is changing the setting from "Does not timeout" to "8 hours" the admin needs to trust the user that he is
logging out so he gets a new session cookie with a new timeout.

## Your Environment
* Graylog Version: Graylog 4.3.0-beta.2+a61a34c

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.