mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 09:46:00 +03:00
[GH-ISSUE #3574] Problem about apache httpd Header Set-Cookie and bitwarden web-v2023.5.0 release #1607
Labels
No labels
SSO
Third party
better for forum
bug
bug
documentation
duplicate
enhancement
future Vault
future Vault
future Vault
good first issue
help wanted
low priority
notes
pull-request
question
troubleshooting
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/vaultwarden#1607
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @ecesarini on GitHub (Jun 11, 2023).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/3574
Subject of the issue
Hi,
upgrading to bitwarden web-v2023.5.0 i'm facing a problem difficult to debug (environment details are in the support string below).
I'm used to set cookie into the client by apache config files
This apache env variable is populated by a pre-authentication action (e.g. via shibboleth). In the code above %{uid}e serves as an example only. The same behavior is obtained using the variable %{mail}e, and the set cookie becomes null.
Since web-v2023.4.0 or web-v2023.4.2 the process has always worked fine. Starting from web-v2023.5.0 update cookie is nullified after few moments the page is loaded.
My CookieMail cookie in the browser is (null) when the service is loaded, but the browser get the right cookie back if i reload the refresh itself.
I'm trying to understand if this behaviour could depends on vaultwarden/server, but i'm not sure; so forgive me if this open issue may sound inconvenient.
Deployment environment
Your environment (Generated via diagnostics page)
Config (Generated via diagnostics page)
Show Running Config
Environment settings which are overridden:
Troubleshooting data
In the attachement images there is a comparison.
expected: web-vault-2023.4.0 vs issue: web-vault-2023.5.0