Skip to main content
With Custom Auth, users who are already signed in to your app skip the AIR Kit login method picker. Your backend signs a Partner JWT that includes the user’s email, and your app passes it to login({ authToken }). AIR Kit then creates or loads the AIR Account for that email. Custom Auth is often a JWT followed by an email one-time password (OTP), not a silent login. By default, the first time a user signs in to your app, AIR Kit sends an OTP to the email in the JWT and asks the user to enter it, because the email identifies the user across AIR. Only after that does AIR issue the session. Later logins to your app with the same email skip the OTP.
For customization, please contact the AIR team.
Custom Auth needs a registered JWKS endpoint, like any Partner JWT.

JWT payload

Sign the token on your server with a kid header that matches your JWKS. For a full implementation with backend and frontend code, see the Bring your own auth recipe.