I am facing a wierd problem. I installed policy server which is pointing to an LDAP policy store. I was able to successfully test the connection to the policy store from the policy server. I also registered the siteminder super user using the XPSRegClient utility on the policy server host. Then I installed wamui on another server. Now, when I try to login to the admin ui, I get the error Invalid username password combination even though I provide the correct credentials.

I tried reinstalling the components several times but no luck. Can you help?

Thanks in advance – Sudhir.

we have been hit by another performance issue now. Openign SiteMinder UI or OID-ODSM console is taking enormous time. It seems CA Siteminder guys have got a new CR009 for R12SP3. So i am going to install that patch and then see if the performance issue gets resolved..

Forgot to mention “Thanks Todd” …

We have got a solution for this error.

BY default SiteMInder searches for XPS data only for 20 seconds. We had 29900 data entries for xpsNumber and hence we had to increase the default timing in sm.registry by 10 mins (600s).

The “SearchTimeout” entry which is not present in the default sm.register was updated as below :

HKEY_LOCAL_MACHINE\SOFTWARE\Netegrity\SiteMinder\CurrentVersion\LdapPolicyStore=20495
AdminDN= cn=orcladmin; REG_SZ
AdminPW= {RC2}4BJMPQgYO5BdMBO/lfBA652fTopG4LXK; REG_SZ
AppSdk= 0; REG_DWORD
CertDbPath= ; REG_SZ
Enabled= 0×1; REG_DWORD
PSRootDN= dc=dcbok; REG_SZ
Server= 172.16.82.71:3060; REG_SZ
Use SSL= 0; REG_DWORD
Version= 5.0; REG_SZ
SearchTimeout= 600; REG_DWORD

Thanks. Do we have any command for re-indexing ?
As i had reindexed all the XPS related attributes via catalog and could see in the LDAP browser that all these attributes are indexed. However, after restarting the OID and SiteMinder services again i faced the same issue as below:

————
[2380/21][Mon Jan 16 2012 23:26:28][CA.XPS:LDAP0018][INFO] LDAP Provider Version: orcldirectoryversion = OID 11.1.1.5.0
[2380/21][Mon Jan 16 2012 23:26:28][CA.XPS:LDAP0018][INFO] LDAP Provider Version: supportedldapversion = 2
[2380/21][Mon Jan 16 2012 23:26:28][CA.XPS:LDAP0018][INFO] LDAP Provider Version: supportedldapversion = 3
[2380/21][Mon Jan 16 2012 23:26:28][CA.XPS:XPSIO039][INFO] Database Transactions are OFF.
[2380/21][Mon Jan 16 2012 23:26:29][CA.XPS:XPSIO007][INFO] 2 Parameter(s) loaded from Policy Store, 2 total.
[2380/24][Mon Jan 16 2012 23:26:31][SmPolicyServer.cpp:1895][INFO] Starting key management thread
[2380/28][Mon Jan 16 2012 23:26:31][SmPolicyServer.cpp:1512][INFO] Key management thread started.
[2380/25][Mon Jan 16 2012 23:26:43][SmPolicyServer.cpp:1459][INFO] Starting journal management thread
[2380/29][Mon Jan 16 2012 23:26:43][SmPolicyServer.cpp:1408][INFO] Journaling thread started, will delete commands older than 60 minutes
[2380/21][Mon Jan 16 2012 23:26:49][smldaputils.cpp:880][INFO] Failing back LDAP store type #0 to server ’172.16.82.71:3060′.
[2380/21][Mon Jan 16 2012 23:27:09][CA.XPS:LDAP0014][ERROR] Error occurred during “SearchExt” for “(xpsNumber=*)”, text: Timed out
[2380/21][Mon Jan 16 2012 23:27:09][CA.XPS:XPSIO008][INFO] 0 object(s) loaded from the Policy Store.
[2380/21][Mon Jan 16 2012 23:27:09][CA.XPS:XPSIO026][INFO] Policy Store ID is “73942492-97a5-1004-bf2e-84f9fe800000″.
[2380/21][Mon Jan 16 2012 23:27:09][CA.XPS:AUDIT012][INFO] XPS Auditing is enabled.
[2380/21][Mon Jan 16 2012 23:27:18][CA.XPS:EDIT0056][INFO] No validation warnings will be logged (controlled by CA.XPS::$LogValidationWarnings).
[2380/20][Mon Jan 16 2012 23:27:30][SmObjStore.cpp:303][INFO] Key Update Management is not enabled
[2380/20][Mon Jan 16 2012 23:27:30][SmObjStore.cpp:345][INFO] Key distribution has been initiated by Policy Server
[2380/31][Mon Jan 16 2012 23:32:39][smldaputils.cpp:880][INFO] Failing back LDAP store type #0 to server ’172.16.82.71:3060′.
[2380/31][Mon Jan 16 2012 23:32:59][CA.XPS:LDAP0014][ERROR] Error occurred during “SearchExt” for “(&(xpsNumber=*)(!(xpsCategory=1))(modifytimestamp>=0))”, text: Timed out
—————————
This is the result after cheking whether all the XPS related attributes are indexed or not in OID. Although i am unaware of any re Indexing commands in OID (If Any).
Pls suggest if there is any breakthrough to this. As the SiteMinder comes up, it completely freezes OID and SiteMinder UI as well.

Thanks in advance.

Anpother clarification: As in OID i can see that the following attributes are indexed:
xpsNumber
XPSCategory
xpsTombstone
xpsIndexedObject
xpsParameter
xpsKeyValue
xpsValue
xpsTombstone
xpsSortKey and
modifytimestamp

However, should i go ahead and index them through Catalog again ?

We can see that these attributes are indexed OID. However, i didnot get which are the directories you have mentioned to be indexed.?