selang "so dh+(..) command doesn't add dh in the correct order

Products

• CA Privileged Access Manager (PAM)
• CA Privileged Access Manager - Cloakware Password Authority (PA)
• CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

When we use selang with the command "so dh+(DH1,DH2,DH3,DH4) , but dh4 takes the second position instead of 4th position. the result in selang of " so list " is

DH1

DH4

DH3

DH2

 

Environment

Release : 14.1

Component : PAM SERVER CONTROL ENDPOINT WINDOWS

Cause

The addition of distribution hosts are not defined as expected. Due to the method of indexing in the seos database as each additional node is added to the list of distribution hosts it will add each additional node as the second node forcing each node to move down the list by 1. so node 2 becomes node 3 and node 3 becomes node 4. 

Resolution

While the behavior may not be obvious you can control the load order policy fetcher will follow by entering your additional DH hosts in reverse order as demonstrated below. The order in which it is displayed with the "so list" command is the load order policy fetcher will follow.

 

AC> so DH+(DH4,DH3,DH2)

(localhost)

Successfully updated CA ControlMinder options

AC> so list

(localhost)

DH                :

    DH1

    DH2

    DH3

    DH4