Workarounds: Creating IM Directory fails when integrated with Siteminder 12.0 and 12.5

Document created by william.k.lee Employee on Jun 24, 2014Last modified by william.k.lee Employee on Jun 25, 2014
Version 2Show Document
  • View in full screen mode

There have a been a series of issues opened with support where the IM directory cannot be created from the management console when IM is integrated with Siteminder 12.0 and 12.5.

 

When creating a SiteMinder integrated IM Directory, the IM application server first creates a copy of the directory object in the IM object store and then does a post-create step using the SetLinkedData method to create a copy of the directory object in SiteMinder’s policy store. It’s in this post-create step that error occurs.

 

Typically, you’ll see a postCreate failure, “object not found” or “duplicate object ID” in the errors. None of these errors accurately describe the problem, nor the solution.

 

CA is working to resolve these problems in a future release.

 

But in the interim, here are the typical resolutions for this scenario:

 

  • If you are SM 12.5, you must import the idmSm.xdd file, or you will see this error.
  • IM searches for auth scheme called Basic to be used as a template for its new auth schemes if this does not return the object the IMS environment will fail to be created.
  • If you already have IM environments or directories that are created that are NOT integrated with SM, the new creation of an integrated directory will fail. Typically, this only happens in dev/test, as there are few real world scenarios where you would have mixed environments like this.
  • If for some reason, the SiteMinder server cannot establish the underlying user directory LDAP connection, you will get this error. Typically, this would be due to firewall problems where IM can reach the server, but SM cannot.
  • Related to this, if the directory.xml file has the <directorySearch timeout=”***”> value set, it appears that IM sees this value in seconds, but SM treats this value as milliseconds. So, if this number is set at 300, IM will connect successfully, but SM may timeout as it may not connect in 300 milliseconds. The workaround here is to set the timeout to “0” which is an infinite amount of time, or to a high value like 100000.

 

William Lee
Principal Support Engineer

Attachments

    Outcomes