Skip to main content

Pass signed-in visitors to a microsite

When a subscriber is already signed in to your own portal or app, you can hand that identity to a microsite without asking them to log in again. Your system generates a short-lived signed token that names the subscriber and proves it came from you; the microsite validates the signature and treats the visit as authenticated.

Before you begin​

  • A shared secret or signing key issued for your account. (Confirm where this is stored and how to rotate it in your account.)
  • The target microsite URL and the identity fields it expects (for example a subscriber ID or email).
  • A place in your own back end to build and sign the token — never sign in browser-side JavaScript, or the secret leaks.
  • Access to test with a non-production subscriber before going live.

Steps​

  1. In your back end, assemble the identity payload for the signed-in visitor (for example their subscriber ID and any attributes the microsite needs).
  2. Add a short expiry (a few minutes is typical) so an intercepted token cannot be replayed later.
  3. Sign the payload with your account signing key to produce the token. (Confirm the exact signing algorithm and field names in your account.)
  4. Redirect the visitor to the microsite URL with the signed token attached as the agreed parameter.
  5. The microsite validates the signature and expiry, then renders personalized content for that subscriber.

Result​

The visitor lands on the microsite already recognized — no second login — and any personalization tokens resolve to their data. Reject and log any token that fails signature or expiry checks.

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