SDKs & apps
The SenseCrypt Authenticator mobile app for end users, and how to integrate your own web application as a relying party.
There are two sides to a SenseCrypt integration: the end-user app that performs the biometric ceremony, and your application that speaks OIDC or SAML.
For end users: the Authenticator app
The SenseCrypt Authenticator is the mobile app (iOS and Android) your users install to approve sign-ins with a face scan. It is the end-user app — you do not embed it in your product. Your users install it from the App Store or Google Play.
For your application: relying party
Your web app integrates as a standard OIDC relying party (or a SAML SP). You do not need a SenseCrypt-specific SDK — any conformant OIDC/SAML client library works. See Relying party for how to think about it, then the Add Login quickstart for the concrete steps.
Pages
- Mobile (Authenticator) — the end-user app and how enrollment works.
- Relying party — integrating a web app over OIDC.
Security best practices
Harden your SenseCrypt integration — redirect-URI hygiene, PKCE, secure token storage, refresh-token rotation, session management, JWT validation, and app attestation.
Mobile (Authenticator)
The SenseCrypt Authenticator app for iOS and Android — the end-user app that approves sign-ins with a face scan. Integrators do not embed it.