A specification for a well-known URL that redirects to a site's password change form, enabling password managers to directly navigate users.
A Well-Known URL for Changing Passwords is a web specification that defines a standardized location (`/.well-known/change-password`) where websites can redirect users to their password change forms. It solves the problem of password managers being unable to reliably help users update passwords because change form URLs are often unpredictable and hidden. By implementing this URL, sites enable password managers to offer direct, one-click access to password change pages.
Website developers and operators who want to improve the user experience for password updates, and developers of password managers or security tools that need to programmatically locate password change forms.
It provides a minimal, standards-based solution that requires almost no ongoing maintenance once implemented, and it's already supported by major password managers and browsers, offering immediate utility without complex configuration or additional dependencies.
A Well-Known URL for Changing Passwords
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Uses the established RFC 5785 .well-known/ mechanism to provide a predictable, site-wide URL for password changes, ensuring consistent location across websites as outlined in the specification.
Requires only a simple HTTP redirect (3xx) or direct serve (2xx) to an existing password change page, minimizing development effort and maintenance, as emphasized in the proposal.
Already integrated into major password managers like 1Password and browsers like Safari and Chrome, offering immediate user benefits without additional configuration, per the FAQ listing.
Deliberately avoids over-engineering by focusing solely on password changes, keeping the specification lightweight and easy to adopt, aligned with the design philosophy of doing 'the simplest possible thing'.
Only addresses password changes, explicitly excluding other account management functions like profile updates or security settings, as noted in the FAQ's rejection of a JSON resource for broader use.
Requires server-side configuration to set up the redirect, which can be challenging on platforms with restricted access to .well-known directories or when dealing with legacy systems.
Relies on HTTP response codes (2xx or 3xx) for detection, but servers with unreliable status codes may cause false positives or negatives, necessitating additional workarounds as mentioned in the draft on response code reliability.