Credman now re-merged (was: Splitting "Credential Management"?

# Hodges, Jeff (a month ago)

fyi/fwiw, as MikeW notes in [https://github.com/w3c/webauthn/pull/384#discussion_r109671881](https://github.com/w3c/webauthn/pull/384#discussion_r109671881)...

cough To make things more confusing (but hopefully less confusing in the long term!), I've now folded those two documents back into w3c.github.io/webappsec-credential-management. :)

HTH,

=JeffH

c.f.:

lists.w3.org/Archives/Public/public-webappsec/2017Mar/0016.html

On 3/16/17, 6:26 AM, "Mike West" mkwst@google.com wrote:

Hey folks!

While re-reading through the Credential Management API, I realized that the extension mechanisms aren't at all clear. As a thought exercise, I'm mostly finished with splitting the document into a generic API that defines the high-level architecture (w3c.github.io/webappsec-credential-management/base.html), and a document that specifies PasswordCredential and FederatedCredental as an extension (w3c.github.io/webappsec-credential-management/sitebound.html).

WDYT? Is this a sane division? Does it actually make the integration points clearer by forcing us to use them, or is it more confusing than not to have the pieces in distinct documents?

CCing some specific folks who might be interested.

Contact us to advertise here

Want more features?

Request early access to our private beta of readable email premium.