mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-02-05 00:29:40 +03:00
"Your login session has expired." when trying to open an item that belongs to an org #1291
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qbarbe on GitHub (Jun 2, 2022).
Subject of the issue
"Your login session has expired." when trying to open an item that belongs to an org
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Install method: Docker
Clients used: Web vault, Browser extension and Desktop client
Steps to reproduce
Command used to start vaultwarden: docker run -d --restart unless-stopped --name vaultwarden -v /vw-data/:/data/ -e "TZ=Europe/Paris" -e LOG_FILE=/data/vaultwarden.log -e LOG_LEVEL=debug -p 80:80 vaultwarden/server:latest
Login to the web-vault, click on an org, try to open an item.
Expected behaviour
The org's item should open
Actual behaviour
I get logged out as soon as I click on the item with the "Your login session has expired." error, in short: I can't open org items from the web vault.
Troubleshooting data
Logs from /vw-data/vaultwarden.log and logs set to debug.
Also, don't pay attention to the domain configuration check: the domain name I use to access the admin page is the internal one.
@BlackDex commented on GitHub (Jun 2, 2022):
We need a bit more information, like what role does the org user has.
Also, i do not see that specific logout action in the logs you posted.
Could you please try again and see if you can get the 4XX error message from the logs regarding this? (Not the websockets error)
@qbarbe commented on GitHub (Jun 3, 2022):
The org user is an owner.
And the logs I posted above are the ones that appeared right when I tried to open an org item which logged me out.
The log level is set to debug (the read-only section in the admin page says so) and the
vaultwarden.logfile shows the same logs asdocker logs vaultwarden.I also tried with the trace log level and there is no additional logs when I get logged out (I'm reading the logs file using tail -f)
I want to add that I can open org items only from the "My Vault" page, it is only from the orgnanization's page that I get logged out trying to open an item.
@BlackDex commented on GitHub (Jun 3, 2022):
What are the collection settings of the user?
What happens if you use an other browser?
Did you have v1.24.0 installed before, and did it worked there? If so, what happens if you revert?
Edit:
If you would be logged-out then i still would need to see something else then a 200 within the logs.
@qbarbe commented on GitHub (Jun 3, 2022):
The user also has the owner role for all the collections if that's what you meant by collection settings.
I tried using Firefox and Chrome and it didn't change anything, I still got logged out.
I did have 1.24.0 before but I don't think I've tried to use the web vault to access org items.
I tried reverting to 1.24.0 and I still got logged out.
And here are the logs (trace) that appeared when I got logged off
@BlackDex commented on GitHub (Jun 3, 2022):
I'm not seeing any 4XX errors in the logs, which would need to occur if you were forced to logout.
What does the Browser Developer Console (F12) tell when you try this? Because i do not see anything in the logs at all.
Also, i see you are not using a reverse proxy, though that should not be that big of an issue, but we know that the SSL part of the HTTP Library we use could have some issues with some types of encryption. If that is the case, i would recommend to add a reverse proxy and see if that helps.
@qbarbe commented on GitHub (Jun 3, 2022):
I am using a reverse proxy (apache2), it was not detected by the diagnostics page because I accessed the admin page using the internal domain name which is not handled by the reverse proxy.
Also, I've checked the logs in the browser's console and I saw that there was a 403 error with this
GET | https://bitwarden.mydomain.tld/api/ciphers/[redacted]/admin
And the issue here is that there is /admin at the end of the URL and I blocked /admin using ProxyMatch on the reverse proxy in an attempt at blocking the vaultwarden admin page from being accessible using the public domain name.
I removed the block and I can now open org items.
Thanks for your help.