Skip to main content

FIDO2 integration prerequisites

To get started, you need the following information available:

  • Instance ID
  • Access Key

For more information on the instance ID and the Access Key, see the Developer documentation.

Relying party​

Before you can integrate WebAuthn, provide the following information about your web application, the relying party:

Relying party name: The name of your choosing, for example: Siven Chocolate Factory.

Relying party ID: The domain or part of the domains of your web applications that you plan to register and authenticate users on, for example: siven.ch.

Origins: The list of the origins of your web application. Each origin has to be explicitly allowed, for example:

  • https://www.siven.ch
  • https://login.siven.ch:9443
  • https://sso.login.siven.ch

As WebAuthn can only be used from a secure context, the origins must be one of the following:

  • A local address: http://localhost.
  • An https:// address on condition that the application provides a valid SSL certificate.
info

The Relying party ID must be a subset of all the origins you intend to use.

For example, the siven.ch Relying party ID matches the https://login.siven.ch:9443 origin, but not the https//bank.ch/ origin.

Autofill UI prerequisites​

To enable the autofill UI feature for passkeys, add the username and webauthn value to any existing autocomplete annotations on the username input field as follows:

<div>
  <label for="username">Username:</label>
  <input name="username" id="loginform.username"
         autocomplete="username webauthn">
</div>

For more information, see passkeys.dev.

Contact Nevis support with the relying party information so that we can configure your Authentication Cloud instance.