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.
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.
It provides generalized, persistent, and highly available storage for sessions and tokens used by AM.
AM uses CTS as the authoritative source for CTS-based sessions and caches these sessions in its memory heap to improve performance.
To handle data volatility, ForgeRock recommends configuring an additional DS server separate from the configuration store to isolate session and token information.
CTS entries are large, around 5KB, but are short-lived.