Sign In with Device

Our React Native SDK offers the easiest way to integrate Cotter's Passwordless Login. You can simply call a function and it does most of the heavy lifting and authentication for you.

Concepts: Learn about how Sign in with Device works.

What you're building

Trusted Devices using Cotter's React Native SDK

Steps

Step 1: Import Cotter as a dependency

Make sure you're using react-native version < 0.63

(Optional) Checkout additional steps for Android, React Native < 0.60, and Manual Installation.

Step 2: Set up Cotter in your Project

To allow Cotter to display modals, wrap your root component with connectCotterWrapper :

Step 3: Register user and trust this device

This method signUpWithDevice will register the user based on the user's identifier to Cotter and then trust the current device.

Step 4: Authenticate from a Trusted Device and Non-Trusted Device

To request an authentication from Cotter's SDK, you would need to call cotter.signInWithDevice . This will automatically detect whether the current device is a Trusted Device or not.

Cotter's SDK will find the user from userEmail , this must be the same as the one used to register the user during sign up.

This function returns oauth_token , including an access_token that you should validate in your backend. You can either:

  • use this access_token to protect all of your API endpoints, or

  • you can use your own session tokens. You'll need to validate this access_token before you generate your session tokens in the backend.

Cotter's SDK automatically stores the OAuth tokens for you. Check out how to get access tokens and logged-in user information.

Trusted and Non-Trusted Device

When an Authentication Event is requested using method TRUSTED_DEVICE, there are 2 possible cases:

Case 1: The current device is a Trusted Device

If the current device is a Trusted Device, it should automatically be approved, and you will receive an access token.

You should see a result that the event is not new, and that it's approved. You'll receive the oauth_token because the user is successfully authenticated, and you can pass this to your backend to authorize access for the user.

Checkout how to verify the OAuth Tokens from Cotter here:

Verifying JWT Tokens

Case 2: The current device is NOT a Trusted Device

We'll cover this in the next guide:

Authenticate from a Non-Trusted Device

πŸŽ‰ You're done!

Last updated