Web features explorer

Web authentication signal methods

Limited availability

The signalUnknownCredential(), signalAllAcceptedCredentials(), and signalCurrentUserDetails() methods of PublicKeyCredential inform authenticators of the state of public key credentials, so that incorrect or revoked credentials may be updated, removed, or hidden.

Browser support

  • Chrome 132 Released on 2025-01-14
  • Chrome Android 132 Released on 2025-01-14
  • Edge 132 Released on 2025-01-17
  • Firefox Not supported Bugs: 2039672
  • Firefox for Android Not supported
  • Safari 26 Released on 2025-09-15
  • Safari on iOS 26 Released on 2025-09-15

Baseline availability blocked since September 2025 by Firefox (14 months)

👍
12

Need this feature?
Leave a 👍 on the feedback issue
Don't forget to also leave a comment explaining your specific use case.

MDN documentation

Specifications

Web Platform Tests (WPT)

View the latest WPT test results for this feature

Developer use cases

  • After a successful [key creation](https://developer.mozilla.org/en-US/docs/Web/API/CredentialsContainer/create) storing the key on the server might fail for a number of reasons: - Client-side network issues - Server-side downtime - The key does not meet the requirements and is rejected - Session timed out In these cases, I would like to use the [`signalUnknownCredential`](https://developer.mozilla.org/en-US/docs/Web/API/PublicKeyCredential/signalUnknownCredential_static) to make sure the end-user does not end up with non-accepted Passkeys in their Credential Manager. After a successful [key creation](https://developer.mozilla.org/en-US/docs/Web/API/CredentialsContainer/create) storing the key on the server might fail for a number of reasons: - Client-side network issues - Server-side downtime - The key does not meet the requirements and is rejected - Session timed out In these cases, I would like to use the [`signalUnknownCredential`](https://developer.mozilla.org/en-US/docs/Web/API/PublicKeyCredential/signalUnknownCredential_static) to make sure the end-user does not end up with non-accepted Passkeys in their Credential Manager. [see original comment]

View as JSON | Edit this feature | Report an issue | Web-features entry: source, dist