Lost your Logintap Account?
Just enter your email.
Sign up
First Name
Last Name
Company website
Business e-mail
Press this link to login into existing account or recover your password.

By submitting this form you agree to legal Terms and Privacy rules. Links for these could be found in footer of this website.

Using Logintap Open ID (SSO)

LoginTap can work as an 0Auth2 based OpenID Connect Single Sign-On service provider.

It needs almost zero work on your side, IF - you have OpenID Connect already available in your system.
1. Steps to launch

1. Register with LoginTap.

2. Create a new Project in LoginTap

3. Enable OpenID for the project

4. Copy/paste tokens into your system's backend


2. Auth points to use Logintap OpenID (SSO)

These are various use examples, however, you might not have any control over how your CMS is using the OpenID Connect protocol. So you may just skip this section.

2.1 No Login, No Pass
2.2 No Password
Enter Login
Press for Mobile Auth
2.3 Second Factor Auth
You Login
& Pass are Correct
Waiting for your Mobile Confirmation
Waiting for your Mobile Confirmation
User is recognised via cookie (or alike), when opening the application. No logins/passwords, all is done through mobile 2FA. The same works for business process auth type cases.

Best for maximum convenience for your users.
User enters login only, presses the Login button, and the rest is done via mobile 2FA.

As a subcase - the user forgot a password, gets quick access with just the login.
User first passes full standard auth with login and password, then the mobile 2FA auto starts.

Best for pure 2 factor auth with maximum security.
3. Important Notes

1. Logintap Service is Anonymous!

We do not have, nor do we provide, any user data, such as names or emails when a new user is connected.

OpenID only substitutes login and password, so your OpenID integration must be done right to specifications - after it receives a new user it must enrich other required fields, such as phone numbers, names, etc.

2. Logintap's OpenID Works for Your Existing Users!

Logintap's anonymity provides not only security but also a great advantage - YOU CAN USE LOGINTAP OPENID AUTH FOR ALL EXISTING USERS, not just to register new ones. In this case, you keep all current user data like existing emails and names, as our system will not return this data from any user.

Your OpenID protocol integration MUST BE DONE RIGHT. Your system must use not only an "email" but also the user's "session ID" as one of the parameters when "gluing" a user data received by a standard OpenID response.

As an example - if your user is registered in your system as "[email protected]", and then switches to Google's OpenID using this same email account, your system will "glue" the old registered user to the new authentication choice and update the old user's data fields. If the user chooses a new Google account, say "[email protected]" your system MUST still be able to recognize the user and "glue" with new authentication credentials (with or without re-writting an email address)

4. Full step-by step instruction

VERY IMPORTANT! The work of OpenID can differ between various CMS systems. Logintap only works just as the integration with this protocol is made by your developers. Please refer to your CMS for various setup ways.

This instruction assumes that you have already registered with Logintap. If not - press Sign Up and check your email.

1. Press "Add New Project" button.

2. The Settings form will appear. You can always access it later from a "Menu" button of each of your projects.

1. Name this Project/site, note that is sometimes visible to your users, so name it properly.

2. DO NOT FILL this - it will be filled in automatically when you activate Open ID for this Project.

3. Check the box - Require Finger and Face, as Logintap's SSO will not function without this maximum-security setting.

3. Scroll down to Enable OpenID
1. Activate the Open ID Connect Provider for this project. The checkbox also inserts the special OIDC callback URL into Basic Settings.

2. Generate two tokens for the OIDC protocol - Application ID and API token. The reason there are two separate buttons - so you can change one of these later on a fly, with as little interruption in service as possible.

3. Copy the three standard OpenID items one by one into your CMS system

4. Add logo to the project (not required)

It is recommended that you add a logo of your website/project. It will be used whenever possible on OpenID forms, to make it clear where users are login in.

Only PNG at least 512 by 512 are accepted.

Refresh settings page if the new logo does not become visible right away.
That is it.
The rest of the setup depends on your CMS. Please refer to tech docs of your system for instructions.