Autocomplete default username (+random password) when creating new entries (or option in generator)

Bump. Perhaps just a drop down with auto populate of the organisation’s two or three most recently utilised usernames…

2 Likes

Bump again - this is a frequent annoyance and it’s really hard to understand why someone so simple and frequently encountered isn’t addressed

3 Likes

Bump. This feature has been requested so many times, I don’t understand why such a simple feature has not been prioritized and implemented yet. Seems like a feature that should definitely exist for a password manager I am paying for.

6 Likes

Created an account to specifically request this. I have been using Bitwarden for 3+ years now! This would be great!

3 Likes

How is this still not a feature?

3 Likes

I thought this topic is new but its been five years and this feature is still missing is this deliberate to make people move to other passwords manager to pusch them toward an expensive one cause this really a feature in every other company and five years is along time so people are frustrated

3 Likes

I contacted support and they told me to vote on this issue in the community forums lol

1 Like

This is a feature that absolutely needs to be added… Surely the vast majority of users all use their email address for a minimum of 80%+ of their logins…? Or at least the same user name across multiple sites!
Consider this a very strong vote for this feature - for me, the only thing missing from BitWarden atm!

Thinking more about this - I can’t help but wonder how many users do not use BitWarden because of this missing simple feature? I know when people ask me for PW manager recommendations I do not recommend BitWarden (despite using it myself) to anyone who’s touchy about ‘easy to use’ apps/tech (ie my mom, older sisters, etc.) and this is definitely part of that issue…

3 Likes

Good point. I have my wife use Google/Chrome password manager, because it’s easy to use, and “secure enough” for what she does. I’d prefer Bitwarden, but I don’t see the “user-friendly application interface” needed for a non-techie.

I use BW, and pay for Premium. It’s safe, secure, and has some great features. But this one feature is SORELY MISSING!

2 Likes

Description:

I would like to request a feature that allows users to set a default email address for the User ID field when creating new password entries. This feature should be configurable through the application settings. When set, this email address would automatically populate the User ID field in the new entry form, enhancing user convenience and efficiency.

Use Case:

  • Efficiency: Users who frequently use the same email address for their logins will save time by not having to repeatedly enter the same information.
  • Consistency: Helps maintain consistency in the entries by reducing the chance of typographical errors in the email field.

Proposed Implementation:

  1. Settings Configuration:

    • Add a new setting in the application settings where users can specify their default User ID email address.
  2. ViewModel Modification:

    • Modify the ViewModel handling new entries to read from the settings and use the default email address if specified.
  3. UI Update:

    • Update the new entry form to automatically populate the User ID field with the default email address from the settings.

Example Configuration File:

A JSON configuration file to store the default email setting could look like this:

{
  "defaultEmail": "[email protected]"
}

Example Code Changes:

  1. ViewModel Code:

    public class AddEditItemViewModel : BaseViewModel
    {
        private string _userId;
        private const string SettingsFilePath = "path/to/settings.json"; // Adjust the path as necessary
    
        public AddEditItemViewModel()
        {
            // Load settings
            var settings = JObject.Parse(File.ReadAllText(SettingsFilePath));
            var defaultEmail = settings["defaultEmail"]?.ToString() ?? string.Empty;
    
            // Initialize properties
            _userId = defaultEmail;
        }
    
        // Property for UserID
        public string UserId
        {
            get => _userId;
            set => SetProperty(ref _userId, value);
        }
    
        // Other properties and methods
    }
    
  2. Settings UI Code:

    <TextBox Text="{Binding DefaultEmail}" PlaceholderText="Default User ID Email" />
    
  3. Settings ViewModel Code:

    public class SettingsViewModel : BaseViewModel
    {
        private string _defaultEmail;
        private const string SettingsFilePath = "path/to/settings.json";
    
        public SettingsViewModel()
        {
            // Load settings
            var settings = JObject.Parse(File.ReadAllText(SettingsFilePath));
            _defaultEmail = settings["defaultEmail"]?.ToString() ?? string.Empty;
        }
    
        public string DefaultEmail
        {
            get => _defaultEmail;
            set
            {
                SetProperty(ref _defaultEmail, value);
                // Save to settings file
                var settings = JObject.Parse(File.ReadAllText(SettingsFilePath));
                settings["defaultEmail"] = value;
                File.WriteAllText(SettingsFilePath, settings.ToString());
            }
        }
    
        // Other properties and methods
    }
    

Benefits:

  • Improves user experience by reducing repetitive data entry.
  • Ensures consistency across password entries.
  • Saves time for users with multiple logins.

Conclusion:

This feature would greatly enhance the usability and efficiency of the Bitwarden application. I believe it would be a valuable addition to the community and I hope the community will consider implementing it.

Thank you for considering this feature request!

6 Likes

A post was merged into an existing topic: Set default account for site

+1

This would be great

1 Like

Any update on this ? It would very nice not to type our email address as user in 99% of new entries… I’m ready to help paying a bounty if it helps.

Apart from that, BW really rocks ! KUTGW !

1 Like

While I understand why people might want this, I don’t think Bitwarden should prioritize implementing a feature that encourages people to give their primary email address to every site they create an account with, as this is not a good practice for security or privacy reasons.

If one of these sites that you have an account with experiences a data breach and your email address gets leaked, you become vulnerable to spam, phishing, or credential stuffing attacks. This is also a common occurrence in the Bitwarden subreddit where people regularly complain that someone is trying to get access to their account, which is only possible in the first place if the attacker knows your email address. People should use random email aliases for most of their accounts if they need to submit their email address when registering for a site. Something like DuckDuckGo is even completely free to use and Bitwarden supports it natively.

We discourage password reuse, so why shouldn’t we do the same for usernames? Since Bitwarden is a security company focused on password management, they should encourage people to use random usernames rather than making it easier to maintain a poor security practice.

However, if Bitwarden implements this, it should be one of the many options in the username generator instead of adding it automatically to all new logins that a user creates.

1 Like

I would like to see the email field linked to the username generator

I also created a community account to request this. I understand that using email aliases is best-practice from a security perspective, but it should at least be an option when creating an account, even if it’s not the default option.

2 Likes

A post was merged into an existing topic: Inline autofill: type to filter

We NEED a way to be ableto set a default username. This has been requested so many times and is extremely easy to implement.

Someone once said it was a security feature to not use the same username… but 95% of websites require you to use your email address as your username, so the omission of this setting can’t be called a security feature.

3 Likes