Certain channels such as Engage Messaging create web-based sessions between the agent and the customer. When creating a community that serves these channels, you need to configure the community’s behavior for using a JSON Web Token (JWT) signed identity. JWT is a standard for securely transmitting information between parties as a JSON object.
You can configure your community to accept, reject, or require signed identities. For example, you configure the community to reject JWT signed identities when you do not want JWT tokens to be used to manage user sessions — for example if you are concerned about the validity of the identities used to establish the sessions. Or, if your company policy mandates the use of JWT signed identities, you may require JWT signed identities.