Authentication and Users
Every user has to authenticate with ConnectyCube before using any ConnectyCube functionality.
When someone connects with an application using ConnectyCube, the application will need to obtain a session token which provides temporary, secure access to ConnectyCube APIs.
A session token is an opaque string that identifies a user and an application.
Create session token
As a starting point, the user’s session token needs to be created allowing user any further actions within the app. Pass login/email and password to identify a user:
Note: With the request above, the user is created automatically on the fly upon session creation using the login (or email) and password from the request parameters.
Important: For better security it is recommended to deny the session creation without an existing user.
For this, set ‘Session creation without an existing user entity’ to Deny under the Application -> Overview -> Permissions in the admin panel.
Authentication via phone number
Sign In with phone number is supported with (Firebase integration).
You need to create Firebase project_id
and obtain Firebase access_token
after SMS code verification, then pass these parameters to login
method:
!> Important note: in order to login via phone number you need to create a session token first.
Authentication via Firebase email
Sign In with email is supported with (Firebase integration).
You need to create Firebase project_id
and obtain Firebase access_token
after email/password verification, then pass these parameters to login
method:
!> Important note: in order to login via email you need to create a session token first.
Authentication via external identity provider
Custom Identity Provider (CIdP) feature is necessary if you have your own user database and want to authenticate users in ConnectyCube against it. It works the same way as Facebook/Twitter SSO.
With Custom Identity Provider feature you can continue use your user database instead of storing/copying user data to ConnectyCube database.
CIdP high level integration flow
To get started with CIdP integration, check the Custom Identity Provider guide which describes high level integration flow.
How to login via CIdP
Once you done with the setup mapping in ConnectyCube Dashboard, it’s time to verify the integration. To perform CIdP login, the same ConnectyCube User Login API is used. You just use existing login request params to pass your external user token:
Once the login is successful, ConnectyCube will create an underalying User entity, so then you can use ConnectyCube APIs in a same way as you do with a normal login. With CIdP we do not have/store any user password in ConnectyCube User entity.
Following further integration, you may need to connect to Chat. In a case of CIdP login, you do not have a user password. In such cases you should use ConnectyCube session token as a password for chat connection. Follow the Connect to Chat with CIdP guide.
Create guest session
To create a session with guest user use the following code:
Session expiration
Expiration time for session token is 2 hours after last request to API. If you perform query with expired token, you will receive the error Required session does not exist. In this case you need to recreate a session token.
There is a special callback function to handle this case:
Destroy session token
To destroy a session use the following code:
User signup
Only login (or email) + password are required for user to be created. All other parameters are optional:
User profile update
If you want to change your password, you need to provide 2 parameters: password
and old_password
. Updated user
entity will be returned.
User avatar
You can set a user’s avatar. You just need to upload it to the ConnectyCube cloud storage and then connect to user.
Now, other users can get you avatar:
Password reset
It’s possible to reset a password via email:
If provided email is valid - an email with password reset instruction will be sent to it.
Retrieve users V2
Examples
Retrieve users by ID
Retrieve users by login
Retrieve users by last_request_at
More information (fields, operators, request rules) available here
Retrieve users V1 (Deprecated)
Retrieve users by ID (Deprecated)
Retrieve user by login (Deprecated)
Retrieve user by email (Deprecated)
Retrieve users by full name (Deprecated)
Retrieve user by phone number (Deprecated)
Retrieve user by external ID (Deprecated)
Retrieve users by tags
Delete user
A user can delete himself from the platform: