# Ceremonies

In the Webauthn context, there are two ceremonies:

* The **attestation ceremony** or **creation ceremony**: associates an authenticator to a user account
* The **assertion ceremony** or **request ceremony**: used for the authentication of a user.

For both ceremonies, there are two steps to perform:

1. The creation of options: these options are sent to the authenticator and indicate what to do and how.
2. The response of the authenticator: after the user interacted with the authenticator, the authenticator computes a response that has to be verified.

Depending on the options and the capabilities of the authenticator, the user interaction may differ. It can be a simple touch on a button or a complete authentication using biometric means (PIN code, fingerprint, facial recognition…).

## Attestation ceremony

This ceremony aims at registering an authenticator. It can be used during the creation of a new user account or when an existing user wants to add an additional authenticator.

![The attestation ceremony](https://1231608457-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoCkxY4ZlMvuztwuQH2nf%2Fuploads%2FdEypG5niXMsIhTpefkJT%2Fregistration.png?alt=media\&token=bcfe5d6c-4499-4b69-8588-b57ea693728e)

## Assertion ceremony

This ceremony aims at authenticating a user. The user will be asked to interact with one of its authenticators. Additional authentication means, such as PIN code or fingerprint, may be required.

![The assertion ceremony](https://content.gitbook.com/content/oCkxY4ZlMvuztwuQH2nf/blobs/iotL9YP9sF5bcvONWkbS/login.png)