Invitation confirmation email should use the invitation_org_name in the body

Feature Requests
1

The invitation_org_name environment variable was introduced in commit 8867626. This is a wonderful customization feature, but it would be great if the invitation confirmation email displayed this as well.

With the most recent release, the confirmation email still shows, in bold, bitwarden_rs.

Can this be changed?

2

Are you sure you have changed it?
I just tested it and works fine.

3

I had to double check. I went through the process and spun up a second instance and copied my config making sure that invitation_org_name was set. Here’s the process I took to replicate the issue.

For this example, invitiation_org_name = “Bitwarden at mysite.com”

  1. Invite a user from the admin panel
  2. Email arrives from the system. Subject and bold text in the email both show “Bitwarden at mysite.com”.
  3. User clicks on “Join Organization Now” and creates an account.
  4. User receives welcome email providing the URL to the vault.
  5. User logs in.
  6. Email arrives stating New Device Logged In From , and in the same second, a second email arrives with the subject of “Invitation to bitwarden_rs confirmed” and the body states “This email is to notify you that you have been confirmed as a user of bitwarden_rs”.

So my thinking is that it’s only in response to invitations, maybe even just admin invitations but I haven’t went deep enough yet.

Diagnostics

diag
diag890×496 20.8 KB

config.json

(forgive the space between mysite and .com - autoformatting is killing me)

{
“domain”: “xxxx”,
“disable_icon_download”: false,
“signups_allowed”: false,
“signups_verify”: false,
“signups_verify_resend_time”: 3600,
“signups_verify_resend_limit”: 6,
“invitations_allowed”: true,
“password_iterations”: 100000,
“show_password_hint”: false,
“admin_token”:“xxxx”,
“invitation_org_name”: “Bitwarden at mysite .com”,
“ip_header”: “X-Real-IP”,
“icon_cache_ttl”: 2592000,
“icon_cache_negttl”: 259200,
“icon_download_timeout”: 10,
“icon_blacklist_non_global_ips”: true,
“disable_2fa_remember”: false,
“authenticator_disable_time_drift”: false,
“require_device_email”: false,
“reload_templates”: false,
“log_timestamp_format”: “%Y-%m-%d %H:%M:%S.%3f”,
“disable_admin_token”: false,
“_enable_yubico”: false,
“_enable_duo”: false,
“_enable_smtp”: true,
“smtp_host”: “xxxx”,
“smtp_ssl”: true,
“smtp_explicit_tls”: true,
“smtp_port”: 465,
“smtp_from”: “xxxx”,
“smtp_from_name”: “Bitwarden Admin”,
“smtp_username”: “xxxx”,
“smtp_password”: “xxxx”,
“smtp_auth_mechanism”: “login”,
“smtp_timeout”: 15,
“smtp_debug”: false,
“smtp_accept_invalid_certs”: false,
“smtp_accept_invalid_hostnames”: false,
“_enable_email_2fa”: true,
“email_token_size”: 6,
“email_expiration_time”: 600,
“email_attempts_limit”: 3
}

4

This should be fixed in

1 Like
5

Ah, thx for the clear explanation @blackhatrob,that was very useful.

And thx @jjlin for fixing it this fast.

I have it merged already and should be in the testing tagged image soon.

1 Like
6

Awesome, thanks for fixing this relatively minor cosmetic issue so quickly!

1 Like