The Working Group rechartered in April 2022 with updated scope:
The Working Group will determine use cases that the API needs to support and use these to derive requirements. Success will be determined by the implementation of API features as defined in this section of the charter.
API Features in scope are:
- Requesting generation of multiple asymmetric key pairs within a specific scope (e.g., an origin) with crypto (signature and curve) agility and crypto parameter selection;
- Proving that the browser has possession of a specific private key, where the proof can only be done within the scope of the key pair. In other words, authentication should obey the same origin policy;
- Remote desktop (unattended operation) ability;
- Ability to allow a non-modal UI;
- Binding of ambient credentials;
- Re-authentication from the discretion of the relying party;
- Dynamic linking of authentication credentials;
- Storing of private key(s);
- Account recovery and/or credential backup options;
- Facilitate relying party adoption through additional API enhancements such as returning transport indications in assertions, a credential “durability” signal, and credential status feedback signaling from relying parties.
