Where is the password generator?

Hi everybody!
I held back on v8 for a long time on Windows but made another try now.

That the password generator in the client is missing makes it a very painful experience, especially for cases where the Browser is not already opened (yes this still occurs) or the password gen from the browser extension is unable to copy the password to the global clipboard, for usecases like copying the password to another RDP session.

Right now I settled on opening the full client, creating a new password item, creating a new password in there, copying the password.
This is a very lengthy process, which lets any performance and usability improvements which were done back in v7 look like a joke.

I hope there will be an easier solution to that in the future 🙂

What is with this trend of releasing a half-baked, Electron-based "upgrade" to an already working app? Evernote and 1password are two apps I rely on heavily, with ingrained workflows, and both have gone down this road.

Hi folks, thanks for your feedback about the password generator, in app.

I can't make any promises about when or if the password generator will make a return in a similar form as 1Password 7, but I've added your thoughts to the item we're tracking internally.

Currently, using the password generator in 1Password in the browser is the best solution: Create a custom password

ref: IDEA-I-298

Just moved to v8 and very disappointed to see no password generator. The development assumption that password generation is expressly linked to creation of a new item is faulty logic and inherently flawed. Many use cases exist for needing to do password generation outside of a created and maintained item. Please add the functionality back to the Windows app. If you're at a loss for how to invoke it, simply add a line for it in the "3-dots" root menu.

Here is what is required for Jack's earlier suggestion to use the app:
1. Click new item
2. Select a new item type
3. Move to the password field
4. Click on create new password
5. Accept and/or modify the password-generation parameters
6. Select the generated password
7. Copy the generated password
8. Try to close the "temporary" new item
9. Validate with 1P to discard changes (yet another click)

Should require only 1/3 of those steps at most

I also miss the frequently used password generator in the notification area and I appreciate if it comes back soon.
I wonder why one would spend extra working hours to remove a perfectly working feature. Using the browser addon or switching back to v7 are inconvenient for me.

Possible examples of legitimate reasons to use the password generator outside of creating a new login:

• When you need to change a password for an existing login.
• When a new accounts' password policy is not clear. (requiring you to recreate many new passwords until you figure out what it is!)

Also, am I missing something or has the tickbox for ambiguous characters been removed?

Hello again folks, thanks for the additional feedback letting us know that you'd like to see the password generator appear back in-app in a manner other than through editing an item. As previously noted, the current best use of this feature is by using the password generator in 1Password in the browser. @brianglett, and @paxmundi, I've added you votes.

ref: IDEA-I-298

@Loopvogel, we appreciate the additional examples provided.

Also, am I missing something or has the tickbox for ambiguous characters been removed?

The option to Allow ambiguous characters is not available in 1Password 8 or 1Password in the browser. Are you running into a specific issue where a return of this option would help? Can you please provide some additional details and we'd be happy to pass your feedback along to the team. Thanks!

Hi, any progress on bringing back password generator ?

Hello @k121,

Thanks for chiming in here with your interest in seeing the password generator making a return to the app. We have no updates to provide, but I have included a +1 for you letting the product team know this is something you'd like see. 👍

Ambiguous characters:

Oracle databases baulk at passwords containing the 'at' symbol (@).
Linux shells baulk at passwords containing the 'dollar' symbol ($). [I think, if not Linux, someplace else that I've encountered]

I've certainly experienced issues with some symbols in a password entered via certain websites.