--- title: "FIDO2 ceremonies" slug: "fido-ussdk-igfido2-fido2-ceremonies-3-4" updated: 2026-11-11T09:46:33Z published: 2026-11-11T09:46:33Z canonical: "docs.onespan.com/fido-ussdk-igfido2-fido2-ceremonies-3-4" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # FIDO2 ceremonies FIDO2 provides the following ceremonies: - Registration - Authentication ## FIDO2 registration ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/FIDO2_registration.png?sv=2026-02-06&spr=https&st=2026-11-16T16%3A49%3A42Z&se=2026-11-16T17%3A49%3A42Z&sr=b&sp=r&sig=1LnP9uS0XLUe9GuxwiBveYkIaDvAnKjnUGUhveKWbho%3D) Figure: FIDO2 registration ceremony 1. The client initiates the registration ceremony using the dedicated API endpoint of the relying party. Internally, the endpoint calls the `Registering.generatePublicKeyCredentialCreationOptions()` SDK method. 2. The FIDO2 server returns a `PublicKeyCredentialCreationOptions` object, which contains the RP and user data, a challenge, the authenticator selection etc. 3. The client-side JavaScript invokes `navigator.credentials.create()` of the WebAuthN API in the web browser. 4. The client submits the RP and user data as well as a client data hash of the operation, challenge, and the origin to the roaming authenticator. 5. The authenticator challenges the user for verification. 6. The authenticator generates a new key pair for the user and a signature. 7. The authenticator returns the credential identifier, the public key, and the attestation object to the client. 8. The client finalizes the registration using the dedicated API endpoint of the relying party. Internally, the endpoint calls the `Registering.finalizeRegistration()` SDK method. 9. The FIDO2 server validates the signature and, if valid, stores the public key associated with the user. This completes the registration ceremony. Refer to the relying party endpoints implementation in the sample web application for examples of how to implement the REST API of the relying party ## FIDO2 authentication ![](https://cdn.document360.io/038f59a7-abd0-4c14-9de7-3434d28b49fd/Images/Documentation/FIDO2_authentication.png?sv=2026-02-06&spr=https&st=2026-11-16T16%3A49%3A42Z&se=2026-11-16T17%3A49%3A42Z&sr=b&sp=r&sig=NkN4Lyx9tk0qExw%2F5HnnrIK%2B3uPjAeIhoWkAGiQytiM%3D) Figure: FIDO2 authentication ceremony 1. The client initiates the authentication ceremony using the dedicated API endpoint of the relying party. Internally, the endpoint calls the `Authenticating.generatePublicKeyCredentialRequestOptions()` SDK method. 2. The FIDO2 server returns a `PublicKeyCredentialRequestOptions` object, which contains the RP identifier, a challenge, timeout parameters etc. 3. The client-side JavaScript invokes `navigator.credentials.get()` of the WebAuthN API in the web browser. 4. The client submits the RP identifier and a client data hash of the operation, challenge, and the origin to the roaming authenticator. 5. The authenticator challenges the user for verification. 6. The authenticator generates an assertion signed with the user's private key. 7. The authenticator returns the authenticator data and the signature to the client. 8. The client finalizes the authentication using the dedicated API endpoint of the relying party. Internally, the endpoint calls the `Authenticating.finalizeAuthentication()` SDK method. 9. The FIDO2 server validates the signature with the user's public key it has already stored. This completes the authentication ceremony. Refer to the relying party endpoints implementation in the sample web application for examples of how to implement the REST API of the relying party