Click any tag below to further narrow down your results
Links
@kittl/sdk-backend handles authentication on your server by verifying short-lived JWTs from Kittl users, keeping sensitive auth logic out of the browser sandbox. It gives you a `KittlSDK` class to validate tokens and optional external key storage for serverless/edge environments.
- Frontend calls `kittl.auth.getUserToken()` to get a JWT, sends it to your backend, where `KittlSDK.verifyUserToken()` validates it before processing the request
- Token verification returns `payload.sub`, a pseudonymous per-app user ID that stays consistent for each user across sessions
- External signing key caching is required for serverless, edge, and autoscaling runtimes where in-memory caches don't persist between requests