Three methods
Sign-in approval in Tenon Authenticator, with number matching. Authenticator codes (TOTP) from any authenticator app. Email codes for users who can’t use an app.
Tenon-Auth for developers
Add a second step to your application's sign-in, with an authenticator app, sign-in approval on the phone, or email codes. Your server calls the Tenon-Auth API through an SDK, and Tenon-Auth does the rest.
Four SDKs
Java, TypeScript, Python and .NET. They behave the same way and are tested against the same server.
Account recovery
Recovery codes, helpdesk access passes, and remembered devices. Users who lose their phone are not locked out, and attackers don’t get an easy way around the second step.
Your organization's console
Your Administrators manage users, applications and API keys, and read the audit log at admin.glow-kin.com.
How it fits
Section titled “How it fits”- Your application checks the password, as it does today.
- Its server asks Tenon-Auth for the second step:
beginSecondStep. - Your page asks for a code, or shows a number while the phone approves.
- Your server checks the answer with Tenon-Auth, then signs the user in.
The browser never talks to Tenon-Auth, and your API key never leaves your server.