Proposal: https://example.com/.well-known/modify-credentials

• From: John Wilander <wilander@apple.com>
• Date: Tue, 03 Apr 2018 16:27:12 -0700
• To: "public-webappsec@w3.org" <public-webappsec@w3.org>
• Message-id: <67E35B82-87CC-4F27-87C5-FD49E41D4C32@apple.com>

Hi WebAppSec!

We’re thinking of proposing a well-known URL location where users can change their password or other credentials. Since this working group owns the Credential Management spec, we’d like to get your feedback before we email wellknown-uri-review@ietf.org.

# The problem
When a password/credential manager wants to facilitate a user updating their credentials, there isn't a good way to determine which part of the relevant website to send the user to or to signal to the website that the user's intent is to modify their credentials.

# The proposal
https://example.com/.well-known/modify-credentials as a well-known URL endpoint that signals user intent to modify their credentials. The web server can serve a page at this location or do an HTTP or client-side redirect. The location should be restricted to HTTPS, including any redirects. RFC5785 doesn’t mention scheme restrictions but hopefully we can work that out with the reviewers.

What are your thoughts?

   Regards, John

Received on Tuesday, 3 April 2018 23:27:42 UTC