# Errors and errors :c

**URL:** <https://support.nitrokey.com/t/errors-and-errors-c/5736>\
**Category:** Nitrokeys\
**Created:** [December 19, 2023, 4:08pm UTC](https://support.nitrokey.com/t/errors-and-errors-c/5736 "2023-12-19T16:08:33Z")\
**Posts on this page:** 3\
**Page:** 2

<div class="post-metadata">

**Author:** ![bernd](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/b/977dab/32.png) [@bernd](https://support.nitrokey.com/u/bernd)\
**Post date:** [December 22, 2023, 5:46pm UTC](https://support.nitrokey.com/t/errors-and-errors-c/5736/21 "2023-12-22T17:46:50Z")

</div>

> [@ion](#):
>
> The whole [FIDO2 specification](https://fidoalliance.org/specs/fido-v2.0-id-20180227/fido-client-to-authenticator-protocol-v2.0-id-20180227.html#CTAP2ProtocolOverview)

🤦‍♂️ I may should have been done better searching…

I just skipped it briefly. But as I’ve understood, when a especially a resident credential is generated, the remote party needs to ensure that the key on the Token is valid. This is done by attestation, and either the vendor of the FIDO2 chip or the manufacturer of the Security Key is in that Attestation Certificate Trust Store.

However, by now it seams to me, that with each new (resident) credential a key is generated…

> [Web Authentication: An API for accessing Public Key Credentials - Level 2](https://www.w3.org/TR/webauthn/#sctn-op-make-cred)  
> 7. Once the [authorization gesture](https://www.w3.org/TR/webauthn/#authorization-gesture) has been completed and [user consent](https://www.w3.org/TR/webauthn/#user-consent) has been obtained, **generate a new credential object** :  
> …  
> 7.3. Let `credentialSource` be a new [public key credential source](https://www.w3.org/TR/webauthn/#public-key-credential-source) with the fields:
> 
> ```none
> type public-key
> privateKey privateKey
> rpId rpEntity.id
> userHandle userHandle
> otherUI Any other information the authenticator chooses to include.
> 
> ```

```auto

Thanks again @ion.
```

---

<div class="post-metadata">

**Author:** ![ion](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/i/f1d935/32.png) [@ion](https://support.nitrokey.com/u/ion)\
**Post date:** [December 22, 2023, 8:02pm UTC](https://support.nitrokey.com/t/errors-and-errors-c/5736/22 "2023-12-22T20:02:45Z")

</div>

> [@bernd](#):
>
> However, by now it seams to me, that with each new (resident) credential a key is generated…

I’m not sure what else you expected.

> [@bernd](#):
>
> This is done by attestation, and either the vendor of the FIDO2 chip or the manufacturer of the Security Key is in that Attestation Certificate Trust Store.

Technically the expected level of attestation is up to the platform, and the data/cert exchanged you can see in the demo you performed earlier in the thread. Some info on NK3 attestation is discussed in:

> [@ID-Austria does not accept Nitrokey 3A NFC](https://support.nitrokey.com/t/id-austria-does-not-accept-nitrokey-3a-nfc/5338/1):
>
> ID-Austria is the Austrian government identity provider offering Webauthn and hardware tokens, see [compatible devices](https://www.oesterreich.gv.at/id-austria/haeufige-fragen/allgemeines-zu-id-austria.html#fido-compatible). Site lists “Token, die FIDO2 Level 2 zertifiziert mit WebAuthn unterstützen” When registering with my Nitrokey 3A NFC I get: "A-Trust wants to see the make and the model of the ..." Fehler: Dieser FIDO-Sicherheitsschlüssel konnte nicht verifiziert werden. SessionId: A4\_RXOX................. Is the Nitrokey 3A NFC not FIDO2 Level 2 certified with WebAuthn? If it is, will you…

---

<div class="post-metadata">

**Author:** ![bernd](https://support.nitrokey.com/letter_avatar_proxy/v4/letter/b/977dab/32.png) [@bernd](https://support.nitrokey.com/u/bernd)\
**Post date:** [December 22, 2023, 9:52pm UTC](https://support.nitrokey.com/t/errors-and-errors-c/5736/23 "2023-12-22T21:52:56Z")

</div>

> [@ion](#):
>
> I’m not sure what else you expected.

No expectation, because I did not know what to expect 😉 That’s why I asked “how does it work?”

> [ID-Austria does not accept Nitrokey 3A NFC](https://support.nitrokey.com/t/id-austria-does-not-accept-nitrokey-3a-nfc/5338/1)

Good to know.

[Previous page](https://support.nitrokey.com/t/errors-and-errors-c/5736.md?page=1)
