Skip to content
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

Emergency access sends a lot of emails when the wait time period is reached #2955

Closed
spctechdev opened this issue Dec 4, 2022 · 2 comments · Fixed by #2936
Closed

Emergency access sends a lot of emails when the wait time period is reached #2955

spctechdev opened this issue Dec 4, 2022 · 2 comments · Fixed by #2936
Labels
bug Something isn't working enhancement New feature or request

Comments

@spctechdev
Copy link

spctechdev commented Dec 4, 2022

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

mails

@BlackDex
Copy link
Collaborator

BlackDex commented 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.

https://github.com/dani-garcia/vaultwarden/blob/4aa6dd22bbe853542c2396821648f369d07bb951/.env.template#L121...L127

@BlackDex BlackDex added bug Something isn't working enhancement New feature or request labels Dec 4, 2022
@tessus
Copy link
Contributor

tessus commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants