L
Laine Phillips
Currently the "Forgotten Password" / "Reset Password" workflows email the user's actual password in plaintext (via the {{contact.password}} merge field). I'd like to request a secure password-reset flow instead.
The concern:
  • Emailing a password in plaintext is a known security anti-pattern - email isn't a secure channel, and the password then persists in inboxes where it can be intercepted or forwarded.
  • It also implies passwords are stored in a recoverable (non-hashed) form, which is itself a security risk. Best practice (e.g., OWASP guidance) is to store passwords salted-and-hashed and to never send or display them.
The request:
  • A secure, single-use, time-limited password-reset LINK (token), exposed as a merge field (e.g., {{reset_link}}) that we can drop into the Forgotten Password email.
  • The link should take the user to a page to set a NEW password - the existing password is never revealed.
Why it matters:
  • It's the standard, expected behavior for any modern web app.
  • Many of us bill customers under our own brand and are responsible for our users' data, so plaintext-password emails create real liability.
  • It builds trust with the businesses using our directories.
Happy to provide more detail if useful. Thanks for considering it.