Setting for session.timeout not working for Admin user after upgrade to 4.19
- Langage dominant
- Java
- Étoiles
- 3.1k
- Forks
- 1.4k
- Merge moyen
- 6 j 19 h
- PR mergées (30 j)
- 32
Description
##### ISSUE TYPE
* Bug Report
##### COMPONENT NAME
~~~
UI
~~~
##### CLOUDSTACK VERSION
~~~
4.19
~~~
##### CONFIGURATION
NA
##### OS / ENVIRONMENT
CentOS 7
##### SUMMARY
After upgrade to 4.19, my web UI Session timeout of 30 minutes seems to have no impact when logged in as the admin user. It works for other users. My /etc/cloudstack/management/server.properties file's setting session.timeout=30 - which used to work earlier and session timed out at 30 minutes of inactivity.
Additionally, I am able to close brower tab (in which I am logged in as admin), open a new tab with original URL (copy paste) and it still works without asking to log in as admin - that is a security risk in my mind.
##### STEPS TO REPRODUCE
~~~
From 4.17 upgrade to 4.19. Verify session.timeout=30 in server.properies file
~~~
##### EXPECTED RESULTS
~~~
Timeout occurs as per the /etc/cloudstack/management/server.properties file's setting session.timeout for all users including admin.
~~~
##### ACTUAL RESULTS
~~~
Timeout is not respected when logged in as admin. I left a session open overnight and I was able to start working without login need.
When logged in as non-admin user, the timeout setting works.
~~~
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par le paramètre session.timeout dans /etc/cloudstack/management/server.properties et suivez la façon dont l’interface web gère les sessions des administrateurs et des non-administrateurs après la mise à niveau de 4.17 vers 4.19. Reproduisez le cas d’une inactivité durant la nuit ou pendant 30 minutes, puis vérifiez que les sessions d’administrateur expirent et que la réouverture de l’onglet nécessite une connexion, comme prévu.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- java
- Domaine
- authentication, security
- Type d'issue
- Bug
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Activité
- Active
- Clarté
- Plutôt claire
- Accessibilité débutants
- 45/100