A customer token is a signed JSON Web Token that proves which customer IDs a device may act for. Bloomreach Engagement APIs and SDKs accept it in place of raw customer IDs for features such as App Inbox. Your backend generates it after verifying the login. The `sub` claim holds the customer ID types and values. The `kid` claim names the private API key. The signature is HS256, keyed with the SHA-256 checksum of that key's API secret. The `exp` claim sets an optional expiry. Bloomreach offers no token-generation API because only the website or app backend can confirm who is logged in. The API secret must never ship to a browser or app, and it cannot be recovered once the key is created.
Updated
Category
Bloomreach Dev, Identity
Also known as
advanced customer authentication; customer JWT; customer auth token
In practice
Store the API secret in the backend secret manager at key creation, because it is shown once. Set exp so a leaked token has a short life, and build the refresh path before the mobile release, not after.
Something out of date?