Introduction

Each client device connecting to Bit6 platform needs to be authenticated before it can use communication services.

There are 3 groups of authentication scenarios:

Managed

These authentication methods can be used directly from the client side and do not require any server components for your application.

Username

Users can register and login with a username and a password.

Anonymous

Anonymous user authentication is useful for situations where a user does not have an account, for example, if you want to have chatting with web visitors.

Bit6 app needs to be configured to support anonymous users. This is done with auth_anonymous app setting which can be set via a backend API or the developer portal. It specifies the TTL (time-to-live) value for the anonymous users. After user's TTL value expires, all the user data is deleted from the servers.

Third-Party

Bit6 can leverage third-party authentication providers directly, without any server-side programming on your part.

Facebook OAuth2

A user will be able to sign into your application using his/her Facebook account. To get started:

You can see a live demo of the Facebook authentication with Bit6 in VideoCalls.io apps for iOS, Android and Web.

Google OAuth2

Docs coming soon...

Twitter Digits

With Digits the user can sign into your application using a phone number. During the authentication process, the phone number will be verified via an SMS message or a phone call. The verification process is completely free.

Delegated

In many situations there is already an existing user management and authentication system in place. Bit6 can use it with a simple server-side integration. As the result a user signing into your app will be automatically authenticated in Bit6 platform and can immediately start using communication services.

Overall the process consists of the following steps:

  1. User logs into your client-side app as usual
  2. The app sends an authentication request to your application server
  3. During that process, your server generates a special 'external' JWT token for Bit6 describing the user identity to be used for messaging and calling
  4. On the client side, you can initialize Bit6 SDK and provide it with that JWT token
  5. Bit6 SDK will complete the authentication with the Bit6 Platform

Own App Server

You would need to add a simple token generator to your app server code. Check out the following code samples:

Backend-as-a-Service

If you are using a Mobile Backend as a Service platform instead of hosting your own application servers, the process is exactly the same. You need to add code that will be executed on the backend.

We have the following integration guides available: