System Configuration

The diagram below illustrates the overall architecture of how your service and our service work together.
By delegating the specialized processes involved in authentication to the YubiOn FIDO2 Server Service, you can implement secure and convenient passkey authentication.

Key Components:

• End User: The user who logs into the service.
• FIDO Authenticator: The smartphone, PC, or security key owned by the user.
• Your Service: The website or application that provides services to the user.
• YubiOn FIDO2 Server Service: Our service, which specializes in handling the authentication process.

Roles:

• Your Service: You can focus on user management and your core service functionality. When authentication is required, you simply call our service via an API.
• Our Service API: Handles all the complex FIDO2 protocol processing, public key management, and signature verification.
• Our Service Management Console: Provides an admin console for registration and configuration of our service.

Integration with our service is achieved by embedding the SDK (Software Development Kit) we provide into your service.

The SDK simplifies the complex API communication and protocols of FIDO2, allowing your developers to implement secure and fast authentication by adding just a few lines of code. This significantly reduces development effort and allows you to focus on your core service development.

Role of Each Component

Your Service

• Application Backend
  Provides user management and the core functionality of your service. When authentication is needed, it calls the functions of the YubiOn SDK.

• YubiOn SDK
  A software component that you integrate into your application. It mediates communication with our service and executes complex processes on behalf of your developers.

YubiOn FIDO2 Server Service (Our Service)

Handles all specialized and critical authentication processes, such as FIDO2 protocol processing, public key management, and signature verification.