Skip to main content

# Web component integration

A web component is a tool that enables flawless integration of BAF with a web interface.

#### How It Works​

- The web component operates through an integration created on the server side.

- The integration acts as the entry point, defining the settings and data the component will use.

- Without an integration, the component cannot function.

#### Integration Structure​

- Integrations are linked to accounts.

- Each account can have multiple integrations.

- However, one integration can only belong to one account.

- Integrations function independently, allowing different settings for different integrations within the same account.

Example: One integration may collect biometric data with recorded videos, while another does not.

#### Key Rules​

- A web component can only work with one integration at a time.

- Switching integrations requires restarting the component with new parameters.

- Updating settings: Simply update the integration parameters—no need to modify the component itself.

However, users who have already loaded the component must refresh their page to apply new settings.

#### Domain Verification​

A web component retrieves settings only if the request originates from a domain specified in the integration settings. The system verifies the request headers in this order:

1. Origin – Must fully match the domain in the integration, including schema (e.g., https://example.com).

2. Referrer – Checked like Origin, but the last slash (/) is ignored.

3. Host – Matches only the domain and port.

If both Origin and Referrer headers exist, only Origin is checked.

Multiple integrations can be created for the same domain.

note

Integration management is available only in the dashboard.