-
-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System automatically logs out very fast #4232
Comments
@schris-dk are you sure this is happening on 5.0.14? In 5.0.14 we have actually extended the session to 25 minutes at least. Before it was set to be 5 min. Would you please retry and provide us instructions to reproduce? |
I'm back again :-) I'm still facing the same issue (now v. 5.0.17) - I'm being kicked off after a very short time (<5 min). The issue occours when I'm downloading globaleaks.log from each sub site. During this process, I'm shifting between "the mother site" and the single sub-sites to download the logs. After 4-5 shifts, I'm being kicked off and have to login again I've attached excerpts of Auditlog.csv and globaleaks.log |
Thank you @schris-dk I will try to look into this. You say that you are downloading the globaleaks.log from each subsite, but actually that file is a global file accessible only from the root tenant. What am i missing? |
Hi Giovanni!
It is of course the Auditlog.csv I mean – sorry for the confusion 😊
Med venlig hilsen
Søren Christensen
Senior Manager
Telefon: +4539159901
Mobil: +4530934933
***@***.******@***.***>
BDO Statsautoriseret revisionsaktieselskab
CVR: 20222670
Havneholmen 29
1561 København
Tlf.: +4539155200
www.bdo.dk<https://www.bdo.dk/da-dk/bdo-danmark>
BDO Statsautoriseret revisionsaktieselskab, en danskejet rådgivnings- og revisionsvirksomhed, er medlem af BDO International Limited - et UK-baseret selskab med begrænset hæftelse - og del af det internationale BDO-netværk bestående af uafhængige medlemsfirmaer. BDO er varemærke for både BDO-netværket og for alle BDO-medlemsfirmaerne. BDO i Danmark beskæftiger mere end 1.700 medarbejdere, mens det verdensomspændende BDO-netværk har ca. 115.000 medarbejdere i mere end 166 lande.
Denne e-mail og enhver vedhæftet fil er fortrolig. Hvis du ikke er rette modtager, bedes du venligst omgående underrette os og derefter slette e-mailen og enhver vedhæftet fil uden at beholde kopi og uden at videregive oplysninger om indholdet.
Tænk på miljøet - er det nødvendigt at printe mailen?
Fra: Giovanni Pellerano ***@***.***>
Sendt: 21. oktober 2024 14:50
Til: globaleaks/globaleaks-whistleblowing-software ***@***.***>
Cc: Søren Christensen ***@***.***>; Mention ***@***.***>
Emne: Re: [globaleaks/globaleaks-whistleblowing-software] System automatically logs out very fast (Issue #4232)
Ekstern afsender
Thank you @schris-dk<https://github.com/schris-dk>
I will try to look into this.
You say that you are downloading the globaleaks.log from each subsite, but actually that file is a global file accessible only from the root tenant. What am i missing?
—
Reply to this email directly, view it on GitHub<#4232 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQ5NSMVEWXDCZUEEGGHA5DLZ4TZ6BAVCNFSM6AAAAABPYGSWT2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRWGU3TSNJZHE>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
What version of GlobaLeaks are you using?
5.0.14
What browser(s) are you seeing the problem on?
Chrome
What operating system(s) are you seeing the problem on?
Windows
Describe the issue
During an export of Globaleaks.log files from all hosted sites (one by one), the system automatically logs out after 4-5 downloads, forcing a re-log in.
Each download requires a log in to each site, which takes 30-60 sec, where after I return to the 'mother site' in the other open pane, and open a new 'sub-site'.
As described, each login is only about 30-60 sec, with a prompt return to the 'mother site' - a timespan that shouldn't trigger a 'time out logout'
Proposed solution
Implement a warning that the system will automatically log out in xx seconds if there is no activity - or ability to enable a 'maintenance mode' whith a longer timeout period
The text was updated successfully, but these errors were encountered: