Microsite SSO token reference

Microsite SSO lets a subscriber open a microsite already identified, without a separate login. The platform issues (or accepts) a signed token that carries the subscriber's identity and a short validity window. This page lists the token parameters, the identity claims you can expect to read, and the signing requirements. Exact parameter names and endpoints vary by account configuration — (confirm the exact steps in your account).

Reference

Parameter / claim	Type	Example	Notes
sub	string	subscriber@example.com	The subscriber identifier the token authenticates. Often the email address or an external ID you mapped.
token / signed payload	string	eyJhbGciOi...	The signed token passed on the microsite URL or in a header. Do not log or reuse across subscribers.
iat	timestamp	1751414400	Issued-at time (Unix seconds). Used with the expiry window.
exp	timestamp	1751414700	Expiry time. Tokens are short-lived by design (commonly a few minutes).
aud	string	<microsite-id>	The microsite the token is valid for. A token for one microsite should not be accepted by another.
nonce / jti	string	a1b2c3d4	Single-use identifier to help prevent replay, when enabled.
Custom claims	string	region=EMEA	Additional subscriber attributes you chose to pass through for personalization or gating.
Signature algorithm	string	HS256 / RS256	See Notes — the algorithm and key are set by your account configuration.

Notes

• Signing. Tokens are signed with a shared secret (HMAC, e.g. HS256) or an asymmetric key pair (e.g. RS256). Keep the secret or private key server-side only; never embed it in client code or an Edition. (confirm the exact algorithm and key in your account)
• Validation. Always verify the signature, the exp/iat window, and the aud before trusting any claim. Reject expired, malformed, or wrong-audience tokens.
• Transport. Prefer HTTPS for every request that carries a token. Treat the token as a credential — short lifetimes and, where available, single-use nonce/jti reduce replay risk.
• Clock skew. Allow a small tolerance (typically under a minute) when comparing timestamps so legitimate tokens are not rejected by minor clock differences.
• Personalization. Custom claims can drive gated content or pre-filled fields; pair them with personalization tags for consistent behavior across the Edition and the microsite.

Related

• Microsites and experiences
• Personalization tags reference
• Send a transactional email

---

Canonical terms: Author, Edition, Folder (Project Folder), Broadcast. See the Glossary.