Obscure password during creation

[jgbrwn]

🚀 Feature Request

Hello, fantastic project! I think it would be great to obscure the generated password during creation. I'd guess this should/would also involve adding a copy button somewhere during creation so the creator can copy to clipboard as they will likely need to use/set the pw somewhere. Yes, true if where they are setting the pass shows the inputted password, or if they just paste somewhere from their clipboard they can still see the password, yes, but I think the main issue here is that the creator does not actively see the password during the creation within Password Pusher, with the hopes that whatever needed usage/setting of the pass in whatever application they are using is also obscured. Nothing we can do about where they set it, but this way at least Password Pusher is not actively showing the pass to the creator during creation! (and a nice copy button should appear after creation).

🔈 Motivation

A chief complaint in many orgs is that often the password is known by the creator, so I think this would be a very useful feature

🛰 Alternatives

Note sure if there are any

📎 Additional context

I think if an org would want this feature, it shouldn't be optional/settable in the UI, eg, it should be a docker run env option PWP__PW__ENABLE_BLUR_ON_CREATION true or false or something like that (and if set to true, the creator should NOT be able to toggle/click to unblur. It just needs to be blurred only in that case).

[github-actions]

Hello @jgbrwn, thanks for contributing to the Password Pusher community! We will respond as soon as possible.