In order to use the features of the Chat SDK in your client apps, a SendbirdSdk instance must be initiated in each client app through user authentication with Sendbird server. The instance communicates and interacts with the server using an authenticated user account, and is allowed to use the Chat SDK's features. This page explains how to authenticate your user with the server.
To use our chat features, you must initialize a
SendbirdSdk instance by passing the
APP_ID of your Sendbird application as an argument to a parameter of the
SendbirdSdk constructor method. The
initWithApplicationId: must be called once across your client app. Generally, initialization is implemented in the
By default, Sendbird server can authenticate a user just by a unique user ID. Then the server queries the database to check for a match upon the request for connection. If no matching user ID is found, the server creates a new user account with the user ID. The ID must be unique within a Sendbird application to be distinguished from others, such as a hashed email address or phone number in your service.
This authentication procedure is useful when in development or if your service doesn't require additional security.
Note: Go to the Event handler page to learn more about the usages of the Chat SDK's handlers and callbacks.
Note: You must connect to the Sendbird server before calling any methods through the Chat SDK, apart from initializing a
SendbirdSdkinstance. If you attempt to call a method without connecting, a
ConnectionRequiredErrorwill be returned.
Using Chat Platform API, you can create a user along with their own access token, or issue an access token for an existing user. Once an access token is issued, a user is required to provide the access token when logging in to the Sendbird application.
- Using the Chat Platform API, create a Sendbird user account with the information submitted when a user signs up or into your service.
- Save the user ID along with the issued access token to your persistent storage which is securely managed.
- When the user attempts to log in to the application, load the user ID and access token from the storage, and then pass them to the
- Periodically replacing the user's access token is recommended to protect the account.
Note: From Settings > Application > Security > Access token permission setting in your dashboard, you are able to prevent users without an access token from logging in to your Sendbird application or restrict their access to read and write messages.
Note: For security reasons, you can also use a session token when a user logs in to Sendbird server instead of an access token. See the Access token vs. Session token section from the Platform API guide to learn more.
A user should be disconnected from the Sendbird server when they no longer need to receive messages from an online state. However, the user will still receive push notifications for new messages from group channels they've joined.
When disconnected, all event handlers in a user's client app registered by the
addConnectionEventHandler() methods stop receiving event callbacks from the server. Then, all internally cached data in the client app, such as the channels that are cached when the
getChannel() method of the
GroupChannel is called, are also flushed.
Note: By default, most of the data related to users, channels, and messages are internally cached in the
SendbirdSdkinstance of a user's client app, which are retrieved by the corresponding query instances or received through the event handlers.
updateCurrentUserInfo() method, you can update a user's nickname and profile image with a URL.
Or, you can directly upload a profile image like the following:
Note: A user's profile image can be a
PNG(.png) file of up to 25 MB.