Latest update: 7.1.6
- Overview
- Managed Objects
- Relationships Between Objects
- Define a Relationship Type
- Create a Relationship Between Two Objects
- Configure Relationship Change Notification
- Validate Relationships Between Objects
- Create Bidirectional Relationships
- Grant Relationships Conditionally
- View Relationships Over REST
- View Relationships in Graph Form
- Manage Relationships Through the Admin UI
- Roles
- Use Policies to Validate Data
- Store Managed Objects in the Repository
- Access Data Objects
- Access Data Objects By Using Scripts
- Access Data Objects By Using the REST API
- Define and Call Data Queries
- Upload Files to the Server
- Import Bulk Data
- Data Models and Objects Reference
- Managed Objects
- Configuration Objects
- When To Use Custom Configuration Objects
- Custom Configuration Object Naming Conventions
- Mapping Configuration Objects To Configuration Files
- Configuration Objects File and REST Payload Formats
- Accessing Configuration Objects Through the REST API
- Accessing Configuration Objects Programmatically
- Creating Objects
- Updating Objects
- Deleting Objects
- Reading Objects
- System Objects
- Audit Objects
- Links
- IDM Glossary
Store Managed Objects in the Repository
IDM stores managed objects, internal users, and configuration objects in a repository. By default, the server uses an embedded ForgeRock Directory Services (DS) instance as its repository.
In production, you must replace this embedded instance with an external DS instance, or with a JDBC repository, as described in Select a Repository.
These topics describe the repository configuration, and how objects are mapped in the repository.