JWT identity verification
Optional JWT verification lets your site pass a signed JSON Web Token to the widget so Chatevo knows the visitor’s identity — user ID, email, plan tier — without the visitor re-authenticating in chat.
When to use
Section titled “When to use”| Enable JWT | Skip JWT |
|---|---|
| Logged-in portal or app | Public marketing site only |
| Personalized tool calls (account lookup) | Anonymous FAQ |
| Audit trail tied to user ID | — |
Setup overview
Section titled “Setup overview”- Generate a signing secret in Deployments → widget → JWT verification (or use your IdP).
- Your backend issues a JWT for logged-in users.
- Pass the token when initializing the widget (see JWT embed security).
- Chatevo validates signature, expiry, and claims before accepting messages.
Typical claims
Section titled “Typical claims”| Claim | Purpose |
|---|---|
sub | Stable user ID for logs and tools |
email | Display or CRM context |
exp | Expiry — short-lived tokens recommended |
| Custom | Plan, tenant, locale for tool params |
Secrets and verification keys are never exposed to the browser beyond the short-lived visitor token you issue.
Tool integration
Section titled “Tool integration”Tools can map JWT claims to path/query/body params via server-side context — the model does not receive the raw JWT secret.
Troubleshooting
Section titled “Troubleshooting”| Issue | Check |
|---|---|
| Chat works anonymously but not logged-in | Token passed to widget init; clock skew on exp |
| 401 on widget API | Wrong signing secret between your server and Chatevo |