ForgeRock Core Token Service Guide

This guide shows you how to set up a dedicated Core Token Service store for Access Management (AM). ForgeRock Access Management provides intelligent authentication, authorization, federation, and single sign-on functionality.


ForgeRock Core Token Service Guide - cover page
Brand
ForgeRock
Category
Other
Document type
User Manual
Language
English
Pages
35
File format
PDF
File size
638 KB
Published
31 October, 2023
Updated
31 October, 2023
MD5 checksum
BAB6E5212E716AE48978C4375BC18829

About this manual

This guide explains how to set up and manage the Core Token Service (CTS) token store for ForgeRock Access Management. It covers deployment architectures, token store configuration, token management, and reaper settings. CTS provides persistent, high-availability storage for sessions and tokens, supporting features like OAuth 2.0 and SAML v2.0. The guide recommends isolating CTS data from configuration data to reduce replication traffic and improve performance.

What's inside

  • The Core Token Service
  • Deployment Architectures
  • Configuring CTS Token Stores
  • Managing CTS Tokens
  • CTS Backups and DS Replication Purge Delay
  • Configuring the CTS Reaper
  • Tuning the CTS

Frequently asked questions

What does AM's Core Token Service provide?

It provides generalized, persistent, and highly available storage for sessions and tokens used by AM.

How does AM use CTS for sessions?

AM uses CTS as the authoritative source for CTS-based sessions and caches these sessions in its memory heap to improve performance.

Why does ForgeRock recommend an additional DS server for CTS?

To handle data volatility, ForgeRock recommends configuring an additional DS server separate from the configuration store to isolate session and token information.

What is stated about CTS entry size and lifetime?

CTS entries are large, around 5KB, but are short-lived.

Download PDF (638 KB)