Sync email alias API token across clients

Feature Requests Password Manager
,
1

Feature name

  • Save Username Generator API tokens as a setting of account

Feature function

  • Currently you need to generate API tokens and paste them into every instance of Bitwarden including browser extenstions, it’s not user friendly at all.
  • It’s more optimal to save and bind tokens at Bitwarden server side and request usernames via Bitwarden API using saved user’s token.
  • In future you could use OAuth2 to obtain token even more user friendly: User click in Bitwarden settings “Auth with Fastmail” and grants Bitwarden a permission to generate tokens.
8 Likes
2

Share forwarded email alias API keys to mobile app
I tried desktop to mobile and it doesn’t share

1 Like
3

Also Fastmail API allows you to generate email specifically for exact domain. It brings many small, but useful features. I wrote own Telegram bot to generate Fastmail masked emails, now it looks like this in the Fastmail interface:

изображение
изображение770×550 53.4 KB

  1. It has nice site prefix
  2. It’s showed by which app this masked email was created

It’s also showed as single dedicated official integration with Fastmail:

изображение
изображение750×267 27.3 KB

Hope Bitwarden devs will improve their integration.

4

agree this would be a time saver. granted, there can’t be that many users who are generating usernames with these external services. but for those who do, it’s a great idea to set it once instead of having to do it on each computer, each browser and sometimes each profile that browser.

Also, i could see a use case where most of my browsers should have use name generator 1 but then on one device i want to use generator 2. there should be a way to set it on that device and not have it get overwritten. another idea is that you could save both/all of your API keys and each device will pick the option. And you can always pick a different key on any given device you have.

5

I personally kind of solved a problem for me and made a Telegram bot to generate Fastmail Masked Emails from URLs:
изображение

Because it properly integrates with Fastmail and uses OAuth2 authorization, emails are showed like this (description was assigned automatically):

Screenshots

изображение
изображение749×211 17.2 KB

изображение
изображение758×552 32.1 KB

And integration itself looks like this:

Screenshots

изображение
изображение743×185 16.7 KB

изображение
изображение664×530 28.4 KB

Hope one day we can see this level of integration directly in Bitwarden.

Sources:

6

+1

I have accounts for multiple services, and it would be helpful to not have to find the API keys every time I need access to an alias.

7

+1 I’m a new user (in my 30 day trial) and this API key issue was really frustrating. Is there any progress on resolving?

8

Hi John, just to confirm, while token settings don’t currently sync and only persist per device when unlocked (they are cleared out in the web vault if you close the browser) let us know if you’re experiencing issues with this expected behavior, as we’re monitoring for any bugs. I’ll also be sure to pass your feedback along to the team.

1 Like
9

“they are cleared out in the web vault if you close the browser” that is quite sad…

The way I wanted to use this is via fastmail + my own domain.
I wanted to track the masked mails both in BW and in fastmail.com and disable my email catch all rule.

Unfortunately, cause the API token is not synced and the API token is lost when the browser is closed, think I will have to stick with “Catch-all email”.