Set a redirect from
/.well-known/change-password to the change password page of your website. This will enable password managers to navigate your users directly to that page.
As you may know, passwords are not the best way to manage accounts. Luckily, there are emerging technologies such as WebAuthn and techniques such as one-time passwords that are helping us get closer to a world without passwords. However, these technologies are still being developed and things won't change rapidly. Many developers will still need to deal with passwords for at least the next few years. While we wait for the emerging technologies and techniques to become commonplace, we can at least make passwords easier to use.
A good way to do this is to provide better support for password managers.
How password managers help #
Password managers can be built into browsers or provided as third-party apps. They can help users in various ways:
Autofill the password for the correct input field: Some browsers can find the correct input heuristically even if the website is not optimized for this purpose. Web developers can help password managers by correctly annotating HTML input tags.
Prevent phishing: Because password managers remember where the password was recorded, the password can be autofilled only at appropriate URLs, and not at phishing websites.
Generate strong and unique passwords: Because strong and unique passwords are directly generated and stored by the password manager, users don't have to remember a single character of the password.
Generating and autofilling passwords using a password manager have already served the web well, but considering their lifecycle, updating the passwords whenever it's required is as important as generating and autofilling. To properly leverage that, password managers are adding a new feature:
Detect vulnerable passwords and suggest updating them: Password managers can detect passwords that are reused, analyze the entropy and weakness of them, and even detect potentially leaked passwords or ones that are known to be unsafe from sources such as Have I Been Pwned.
A password manager can warn users about problematic passwords, but there's a lot of friction in asking users to navigate from the homepage to a change password page, on top of going through the actual process of changing the password (which varies from site to site). It would be much easier if password managers could navigate the user directly to the change-password URL. This is where a well-known URL for changing passwords becomes useful.
By reserving a well-known URL path that redirects the user to the change password page, the website can easily redirect users to the right place to change their passwords.
Set up "a well-known URL for changing passwords" #
.well-known/change-password is proposed as a well-known URL for changing passwords. All you have to do is to configure your server to redirect requests for
.well-known/change-password to the change password URL of your website.
For example, let's say your website is
https://example.com and the change password URL is
https://example.com/settings/password. You'll just need to set your server to redirect a request for
https://example.com/settings/password. That's it. For the redirection, use the HTTP status code
303 See Other or
307 Temporary Redirect.
Alternatively you can serve HTML at your
.well-known/change-password URL with a
<meta> tag using an
<meta http-equiv="refresh" content="0;url=https://example.com/settings/password">
Revisit your change password page HTML #
The goal of this feature is to help the user's password lifecycle be more fluid. You can do two things to empower the user to update their password without friction:
- If your change-password form needs the current password, add
<input>tag to help the password manager autofill it.
- For the new password field (in many cases it's two fields to ensure that the user has entered the new password correctly), add
<input>tag to help the password manager suggest a generated password.
Learn more at Sign-in form best practices.
How it is used in real world #
Thanks to Apple Safari's implementation,
/.well-known/change-password, has already been available on some major websites for a while:
Try them yourself and do the same for yours!
Browser compatibility #
A well-known URL for changing passwords has been supported in Safari since 2019. Chrome's password manager is starting to support it from version 86 onwards (which is scheduled for Stable release in late October 2020) and other Chromium-based browsers may follow. Firefox considers it worth implementing, but has not signalled that it plans to do so as of August 2020.
Chrome's password manager behavior #
Let's have a look at how Chrome's password manager treats vulnerable passwords.
Chrome's password manager is able to check for leaked passwords. By navigating to
about://settings/passwords users can run Check passwords against stored passwords, and see a list of passwords that are recommended for update.
By clicking the Change password button next to a password that is recommended to be updated, the browser will:
- Open the website's change password page if
/.well-known/change-passwordis set up correctly.
- Open the website's homepage if
/.well-known/change-passwordis not set up and Google doesn't know the fallback.
What if the server returns
200 OK even
/.well-known/change-password doesn't exist?
Password managers try to determine if a website supports a well-known URL for changing passwords by sending a request to
/.well-known/change-password before actually forwarding a user to this URL. If the request returns
404 Not Found it is obvious that the URL is not available, but a
200 OK response doesn't necessarily mean that the URL is available, because there are a few edge cases:
- A server-side-rendering website displays "Not found" when there is no content but with
- A server-side-rendering website responds with
200 OKwhen there is no content after redirecting to the "Not found" page.
- A single page app responds with the shell with
200 OKand renders the "Not found" page on the client side when there is no content.
For these edge cases users will be forwarded to a "Not Found" page and that will be a source of confusion.
That's why there's a proposed standard mechanism to determine whether the server is configured to respond with
404 Not Found when there is genuinely no content, by requesting a random page. Actually, the URL is also reserved:
/.well-known/resource-that-should-not-exist-whose-status-code-should-not-be-200. Chrome for example uses this URL path to determine whether it can expect a proper change password URL from
/.well-known/change-password in advance.
When you are deploying
/.well-known/change-password, make sure that your server returns
404 Not Found for any non-existing contents.
If you have any feedback on the specification, please file an issue to the spec repository.
- A Well-Known URL for Changing Passwords
- Detecting the reliability of HTTP status codes
- Sign-in form best practices