In the last guide, we covered SDK client initialization mechanics and the need for a generated Access Token. This Access Token is the credential your SDK client endpoints must use to identify and authenticate themselves with the Chat Service.
This Token is generated on your server or backend as you authenticate your user and is then utilized by the Chat SDK client to authorize with the Chat Service.
On your server, we must decide, based on the token request that was sent to us, who the user is and what they should be allowed to do.
To figure out who the user is (their identity), you might use your existing login system, using session cookies, an API token, or whatever mechanism you use to secure API requests or pages today. Who the user is and how you authorize their use will vary from app to app.
If you determine that the user should indeed be allowed to access your Chat application, you will grant your user access to Chat by generating an Access Token as part of your authentication flow. You will then return the token to the user client for use in the Chat SDK.
これはお使いのTwilioアカウントのアカウントSIDで、Programmable Charサービスの作成に使用したものでなければなりません。 チャットサービスを管理します。
This is the Chat Service Sid where your Users, Channels, Messages and other chat related data resides. This is the Chat Service you grant the SDK client access to.
This is the Sid of an API created for your Twilio Account, which is used to sign the Access Token cryptographically. You can create these API keys here.
identity of your User. For example,
firstname.lastname@example.org. For more details around Programmable Chat use of identity, please refer to User Identity & Access Tokens section.
Optional: TTL (Time To Live) Access Tokens are only valid for a period of time, in seconds. The default is
3600 seconds (1 hour), but you can adjust this to your needs up to a maximum of 24 hours.
Once your client receives an Access Token from your server, you can initialize the Twilio Chat SDK and start sending and receiving messages, as covered in the previous guide.