# Using a third-party auth provider

Openfort's signer solution enables user onboarding by integrating with backend solutions and authentication providers that support JWT-based authentication.

## Third-party auth platforms

With this approach, Openfort creates **embedded wallets** on the client and follows the necessary security steps to ensure the smart wallet remains non-custodial.

* **[PlayFab](/docs/configuration/external-auth/playfab)**
* **[Firebase](/docs/configuration/external-auth/firebase)**
* **[Better-Auth](/docs/configuration/external-auth/better-auth)**
* **[Accelbyte](/docs/configuration/external-auth/accelbyte)**
* **[Lootlocker](/docs/configuration/external-auth/lootlocker)**
* **[Supabase](/docs/configuration/external-auth/supabase)**

## Custom auth methods

Openfort offers two options to set up embedded signers with custom auth: one based on the [OpenID Connect](https://openid.net/developers/how-connect-works/) (OIDC) standard, and a generic option that lets you bring your own auth server.

* **[Custom OIDC Token](/docs/configuration/custom-auth/oidc-token)**
* **[Custom Auth Token](/docs/configuration/custom-auth/auth-token)**