Duplicated name in DIRECTORY_SERVER_STICKINESS IMSAdditionalProperties after XPSSweeper integrity report
search cancel

Duplicated name in DIRECTORY_SERVER_STICKINESS IMSAdditionalProperties after XPSSweeper integrity report

book

Article ID: 99528

calendar_today

Updated On:

Products

CA Single Sign-On SITEMINDER

Issue/Introduction

The XPSSweeper reports and it is noticed that the objects appear as duplicated with Identity Manager, as all of them are used when integrating Identity Manager with SiteMinder.

These objects seem to be properties of a User Directory (Container, paging, stickiness,etc), which are related to a User Directory.

It was observed that when Identity Manager is integrated with SiteMinder, when we create a User Directory in Identity Manager, the process creates a matching User Directory in SiteMinder Policy Store too.

There are objects that are duplicated:

[1] 
Object ID: CA.SM::IMSAdditionalProperties@21-de3b50b1-83ad-46fc-82d2-7d1afb355cd7 
Object Name: DIRECTORY_SERVER_STICKINESS 
Object Path: IMSAdditionalPropertiesSet[32-377cc592-1ad6-4be4-8684-22bde8de8285] / IMSAdditionalProperties[DIRECTORY_SERVER_STICKINESS] 
Object Description: 

[2] 
Object ID: CA.SM::IMSAdditionalProperties@21-4f5b061e-68a5-40ce-b8b2-deed410d61d9 
Object Name: DIRECTORY_SERVER_STICKINESS 
Object Path: IMSAdditionalPropertiesSet[32-aa27a1b1-0f4c-4120-aa5d-df239eb8f212] / IMSAdditionalProperties[DIRECTORY_SERVER_STICKINESS] 
Object Description: 

Environment

Policy Server 12.8.x

Resolution

First, determine if these duplicated errors are all referring to the same User Directory object (as there should only have one of each then), or if these are old "orphan" directory objects in the Policy Store.

Second, if these objects pertain to an existing User Directory, remove the duplicated objects accordingly.

For this, use the XPSExplorer tool, and check the current Identity Manager User Directories to see if they are orphaned or duplicated and can be deleted, which can be done from the XPSExplorer tool itself.

This should be solved by renaming the affected objects.

Example as below

From those duplicated objects:

[1] 
Object ID: CA.SM::IMSAdditionalProperties@21-de3b50b1-83ad-46fc-82d2-7d1afb355cd7
Object Name: DIRECTORY_SERVER_STICKINESS
Object Path: IMSAdditionalPropertiesSet[32-377cc592-1ad6-4be4-8684-22bde8de8285] / IMSAdditionalProperties[DIRECTORY_SERVER_STICKINESS]
Object Description:

[2]
Object ID: CA.SM::IMSAdditionalProperties@21-4f5b061e-68a5-40ce-b8b2-deed410d61d9
Object Name: DIRECTORY_SERVER_STICKINESS
Object Path: IMSAdditionalPropertiesSet[32-aa27a1b1-0f4c-4120-aa5d-df239eb8f212] / IMSAdditionalProperties[DIRECTORY_SERVER_STICKINESS]
Object Description:

Rename 1 of them as :

CA.SM::IMSAdditionalProperties@21-de3b50b1-83ad-46fc-82d2-7d1afb355cd7
Object Name: DIRECTORY_SERVER_STICKINESS

to

CA.SM::IMSAdditionalProperties@21-de3b50b1-83ad-46fc-82d2-7d1afb355cd7
Object Name: DIRECTORY_SERVER_STICKINESS-InternalApp

Do the same with the other duplicated found too.

This would solve the issue on SiteMinder (CA Single Sing-On) side.