Closed samuelgoto closed 1 year ago
I like Federated Credential Management, but understand the concerns about the existing CredMan surface.
So I'd propose: Federated Identity Exchange API
I suspect optics of the optics of “Identity Exchange” are not great.
I'm going to close this as resolved, since we went with the status quo for the time being at least.
We picked a name (FedCM) that was deliberately narrow/convoluted/technical to avoid the distraction of an un-necessary discussion.
As we approach broader availability (e.g. chrome origin trials, firefox prototyping it, etc) this seems like a good time to ask ourselves as a group if / whether / which name we'd like to use for this API (it gets harder to change as we go along).
Keeping our current name is a perfectly valid choice, but we figure it would be good for that to be a deliberately choice rather than unintentional.
We need to find some resolution, because we need to know what to call this and we'd like your input on this :)
Here are a few options that occurred to us (either option could work for us):
WebID: taken.A few things to consider:
Web Identity
in a few places in the spec (e.g. the in the .well-known/web-identity configuration file). The more we delay on this decision, the more this will start to get baked into the API design and harder to change (because coordinating between multiple implementors is hard-er).This is a discussion about name, rather than scope: none of the spec scope is changing, we just need to finalize what to call the API under its existing scope defined in the spec.
I'm planning to drive some resolution on this issue at TPAC at the FedID CG, which should give people a few weeks to make suggestions here in preparation.
WDYT?