Directory XML import error on IDM Server with SSO/SiteMinder integration

Products

• CA Identity Manager

Issue/Introduction

When we try to import directory XML we are seeing below error.

2022-01-18 12:28:49,418 ERROR [ims.llsdk.environment] (Thread-377) ImsDirectoryImpl.postCreate 
2022-01-18 12:28:49,418 ERROR [ims.llsdk.environment] (Thread-377) java.lang.NumberFormatException: For input string: "##version"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Integer.parseInt(Integer.java:569)
at java.lang.Integer.<init>(Integer.java:867)
at com.netegrity.llsdk6.imsimpl.ImsApiObject.buildReturnedVector(ImsApiObject.java:878)
at com.netegrity.llsdk6.imsimpl.ImsApiObject.buildReturnedVector(ImsApiObject.java:861)
at com.netegrity.llsdk6.imsimpl.TunnelObject.doPSCreate(TunnelObject.java:540)
at com.netegrity.llsdk6.imsimpl.TunnelObject.doPSCreate(TunnelObject.java:490)
at com.netegrity.llsdk6.imsimpl.ImsDirectoryImpl.postCreate(ImsDirectoryImpl.java:316)
at com.netegrity.llsdk6.imsimpl.ImsDirectoryImpl.postCreate(ImsDirectoryImpl.java:290)
at com.netegrity.llsdk6.imsimpl.jdbcmanagedobject.JDBCDelegatedObject.modifyObject(JDBCDelegatedObject.java:159)
at com.netegrity.llsdk6.imsimpl.BaseObject.modifyObject(BaseObject.java:2064)
at com.netegrity.imsconfig.model.directory.DirectoryObjectModel.persistObjectImpl(DirectoryObjectModel.java:435)
at com.netegrity.imsconfig.model.abstracts.ObjectModel.persistObject(ObjectModel.java:597)
at com.netegrity.imsconfig.model.ObjectModelManager.persistObjects(ObjectModelManager.java:532)
at com.netegrity.imsconfig.ImsConfig.config(ImsConfig.java:352)
at com.netegrity.ims.manage.api.AbstractDeployer.runImsConfig(AbstractDeployer.java:297)
at com.netegrity.ims.manage.api.AbstractDeployer.runImsConfig(AbstractDeployer.java:224)
at com.netegrity.ims.manage.api.AbstractDeployer.runImsConfig(AbstractDeployer.java:184)
at com.netegrity.ims.manage.api.DirectoryDeployer.deploy(DirectoryDeployer.java:85)
at com.netegrity.ims.manage.bean.ConfigToolJob.deployImportDirectory(ConfigToolJob.java:476)
at com.netegrity.ims.manage.bean.ConfigToolJob.run(ConfigToolJob.java:238)
at java.lang.Thread.run(Thread.java:748)

2022-01-18 12:28:49,515 ERROR [ims.llsdk.environment] (Thread-377) Could not delete the directory in SiteMinder.
2022-01-18 12:28:49,515 ERROR [ims.llsdk.environment] (Thread-377) AttributeNotPresentException: This method requires the presence of an attribute which was not provided. The attribute is named smOID.
2022-01-18 12:28:49,519 ERROR [ims.idmmanage] (Thread-377) [facility=4 severity=3 reason=0 status=6 message=Unrecognized command]
ImsDirectoryImpl.postCreate

Also, smps.log and smtracedefault.log will show ERROR:[sm-JavaApi-01260] IMSObjectProviderFactory:getProvider() - error loading provider library]:

This indicates that when the directory creation from IM is attempted, SiteMinder is not able to load the IMS libraries:

[02/14/2022][11:25:13.521][11:25:13][5584][944][SmIMSObjProviderFactory.cpp:72][][][][][][][][][][][][][][][][][][][][][][LogMessage:ERROR:[sm-JavaApi-01260] IMSObjectProviderFactory:getProvider() - error loading provider library][]

Cause

SiteMinder is not able to load the IMS libraries required for IM-SM integration. This is usually caused by missing registry keys that would normally be set when you run the IDM installer on the policy server and select the option to install the Policy Server extensions.

The IDM installer, when run on the policy server to add the "extensions," merely sets the required registry entries below. You may have inadvertently not run the installer on the policy server. Regardless, you can skip the IDM installer on the policy server and instead manually verify and add, if needed, the registry entries described below.

Resolution

--Windows--

Using regedit set these two keys (Note: Both 32 and 64 bit keys must be set in the registry even for 64-bit environments):

 

[HKEY_LOCAL_MACHINE\SOFTWARE\<YOUR_MACHINE>\Netegrity\SiteMinder\CurrentVersion]

"IMSInstalled"="8.0

 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Netegrity\SiteMinder\CurrentVersion]

 

"IMSInstalled"="8.0  

--Linux--
For a SSO Policy Server on Linux there is no need to run the IM installer. Instead you can verify that the following entry exists in sm.registry: 

Verify that the following entry exists in sm.registry:

ImsInstalled=8.0; REG_SZ


The above registry setting is also documented here:


Install CA Single Sign-On Extension