Architecture & Implementation Questions on the Identity Manager Objectstore.

Products

• CA Directory
• CA Identity Manager
• CA Identity Governance
• CA Identity Portal
• CA Risk Analytics
• CA Secure Cloud SaaS - Arcot A-OK (WebFort)
• CLOUDMINDER ADVANCED AUTHENTICATION
• CA Secure Cloud SaaS - Advanced Authentication
• CA Secure Cloud SaaS - Identity Management
• CA Secure Cloud SaaS - Single Sign On
• CA Security Command Center
• CA Data Protection (DataMinder)
• CA User Activity Reporting

Issue/Introduction

This document answers some questions about the objectstore.

Environment

Release:
Component: IDMGR

Resolution

1. When does Identity Manager write to the object store?
   
   Identity Manager reads from the object store most of the time. Identity Manager writes to this database when executing configuration tasks like (Import Roles Definitions, create ProvisioningRoles, Modifying admin tasks and screens etc.) During Identity Manager start-up, there are hardly any writes done to the database other than minor ones like date etc.
   
   
2. Can the garbage collection script that is used to clean-up the task persistence database be used to periodically clean-up the object store database if it gets too big?
   
   Since the object store contains mostly environment screen information, the content is minimal. Also writes to the database are done very minimally. There should not be any need to clean-up this database or use any clean-up scripts unless there is some reasonable justification.
   
   
3. Where is the user id and password stored for the native framework authentication from Identity Manager(when not using Siteminder?) Is it stored in the objectstore?
   
   Regardless of whether the system has been installed with or without Siteminder, the user id and password is stored in the user store and not the objectstore.