mirror of
https://github.com/dani-garcia/vaultwarden.git
synced 2026-04-26 01:35:54 +03:00
[GH-ISSUE #2955] Emergency access sends a lot of emails when the wait time period is reached #1424
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#1424
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 @spctechdev on GitHub (Dec 4, 2022).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/2955
Subject of the issue
Vaultwarden sends too much emails when the emergency access wait time lapses or grantor approve the request
Deployment environment
Vaultwarden version: v1.26.0
Web-vault version: v2022.10.0
Running within Docker: true (Base: Debian)
Environment settings overridden: false
Uses a reverse proxy: true
IP Header check: true (X-Real-IP)
Internet access: true
Internet access via a proxy: false
DNS Check: true
Time Check: true
Domain Configuration Check: true
HTTPS Check: true
Database type: SQLite
Database version: 3.35.4
Other relevant details:
Steps to reproduce
Make an emergency request for another account and wait the time the grantor setted.
Expected behaviour
Only one or some emails to inform that the emergency access is pending
Actual behaviour
The grantor receives a lot of emails when the emergency wait time is reached
Troubleshooting data
@BlackDex commented on GitHub (Dec 4, 2022):
Probably fixed by #2936 .
In the mean time you could change the cron schedule time for both emergency access jobs to the new default i set in that PR.
github.com/dani-garcia/vaultwarden@4aa6dd22bb/.env.template (L121...L127)@tessus commented on GitHub (Dec 4, 2022):
@BlackDex the PR was approved by Dani. Doesn't that mean you can merge it to main?
Once again. just wondering. It always depends on how a project is run.