pglombardo / PasswordPusher

🔐 Securely communicate sensitive information with automatic deletion after a certain number of views and/or time has passed. Track who, what and when with full audit logs.
https://pwpush.com
Apache License 2.0
1.78k stars 329 forks source link

Push the password via Email #2313

Open shnsys opened 4 days ago

shnsys commented 4 days ago

Checklist

❓ Question

How can I [X]?

Is it possible to [...]? We have set up a private instance and would like to know if it is possible to push the password via email directly through the PWPush admin portal.

📎 Additional context

github-actions[bot] commented 4 days ago

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

pglombardo commented 3 days ago

Hi @shnsys - not possible yet but coming hopefully this summer.

shnsys commented 3 days ago

Hi @pglombardo, thank you for the update

Our objective is to create bulk passwords and directly forward them via the PWPush portal. Is there a workaround to achieve this? Where can I find the steps on creating the bulk passwords?

pglombardo commented 2 days ago

I'd like to add the ability to do this end to end but the project isn't there yet.

One potential solution is:

  1. Generate a password in the CLI
  2. Post the generated password to the Password Pusher API
  3. Get back the secret URL
  4. Email the secret URL with an email template from the CLI

For example, this is how you could use the API to generate a push with Password Pusher:

curl -X POST -H "X-User-Email: <email>" -H "X-User-Token: MyAPIToken" --data "password[payload]=mypassword&password[expire_after_days]=2&password[expire_after_views]=10" https://pwpush.com/p.json

Documentation on the API is here and get your API token here.

Alternatively, you could use one of the many OSS CLIs available: https://pwpush.com/en/pages/tools

I hope to have the end to end solution to this maybe this fall. There are some bigger features that have to go out first.

Does this help out at all?