Unable to create siteminder super user using smreg command on Solaris 10 LDOMS 1.1.

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• CA Single Sign-On

Issue/Introduction

Description:

Running smreg -su creates an OID of "12-" and SiteMinder Admin is unable to login to SiteMinder GUI.
Correct result would be a dn stored similar to:
smAdminOID4=12-a166867b-563c-4d62-9c11-b90293c0095b,ou=PolicySvr4,ou=Siteminder,ou=Netegrity,o=smPolicyStore

Policy Server has been installed on a Sun T5240 (LDOM) Logical Domain partition.
The issue exists with LDOMS 1.1 only and does not appear with LDOMS 1.0.

Solution:

This issue occurs when hostid for the LDOMS 1.1 machine is coming as 0, which is a known SUN LDOMS 1.1 issue.
You can confirm the current hostid by running "hostid" command on the failing system.

The hostid is used to create the OID of the objects, so if it is being returned as 0 it fails to create the proper OID and this leads to invalid OID "12-" when running smreg command.

It is necessary to apply the following LDOM 1.1 patches provided by Sun:

• 6711897 hostid is not displayed for guest domains unless explicitly assigned during creation
  
  
• 6670605 Want an interface to set LDoms hostid
  
  
• 6718108 LDoms uses wrong hostid prefix
  
  
• 6734471 Restarting ldmd means hostid in inactive domain gets set to 0

Environment

Release:
Component: SMPLC