Skip to content

Webauthn attestation should be an explicit choice #264

Open

Description

@michaelbeaumont

Currently if the RP requests attestation and the authenticator supplies it, it's included in the response. Ideally this is something the client explicitly confirms they want. I suggest:

Always default to setting CTAP's attestationFormats = ["none"].

Only if the RP sets attestation = "direct":

  • Show a credentialsd-ui toggle to the user whether they want to include attestation that defaults to off
  • Only if the user enables it, forward the webauthn attestationFormats setting over CTAP.

Activity

  1. changed the title [-]Attestation should be an explicit choice[/-] [+]Webauthn attestation should be an explicit choice[/+] on Nov 13, 2026
  2. iinuwa commented on Nov 13, 2026

    @iinuwa
    Member

    This is a good direction. we should consider how this behavior might change between browsers and ordinary apps. Browsers may already draw their own UI to prevent this. If we do this ourselves, we should make sure to coordinate with browsers if that's OK with them, or add an option to allow browsers only to say that "I already showed attestation UI, continue without further prompts," similar to what we need to do for related origins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions