This content has been marked as final. Show 10 replies
At this point OAM is trying to create/configure an Identity Store, OIMIDStore, with the IDSTORE* parameters that you supplied in the input file for the -configOAM step. Ostensibly, the message means that it cannot find any entries with cn attribute under the searchbase shown (maybe they don't exist, or the bind dn doesn't have read privilieges over that branch, etc). Suggest reviewing these parameters, if they look alright could you post the file here (perhaps with host names scrubbed), and say what your stroe is (eg OID, or OVD frontending an ldap).
The Bind DN is cn=orcladmin, so I assume it has all the permissions it needs. I used the same props files on a previous environment. I'm running OAM and OIM BP02.
I did notice that OIMIDStore exists in OAM already, perhaps from a previous attempt? Should I remove it or is it smart enough to deal with that??
IDSTORE_HOST: OID HOST
OAM11G_IDM_DOMAIN_OHS_HOST: OHS HOST
OAM11G_OIM_OHS_URL: OHS URL
I would be tempted to remove OIMIDStore and try again, yes. Given that it's created it, it strongly implies that the settings in it work, otherwise it woulldn't have passed the Test Connection (or internal equivalent) test.
Removing OIMIDStore did not work.
Still experiencing issues. This seems to be a pretty buggy process (the integration steps).
Is editing oam-config.xml directly an option?
Editing the oam-config.xml would be an option of last resort, but not having seen that particular error during the integration (I have seen a few others) I can't say what the answer is. Can you create OIMIDStore in the /oamconsole with the same parameters that you supply in the input file?
Also, do the AdminServer.log or AdminServer-diagnostic.log show anyhting at the time of the failure.
Edited by: ColinPurdon on May 16, 2012 5:55 PM
Yes, I can create OIMIDStore with the same params.
Here's the only thing I See in the adminserver.out file:
<May 14, 2012 5:46:09 PM CDT> <Error> <oracle.oam.user.identity.provider> <OAMSSA-20047> <No entries were found under the User Search Base : cn with attribute : cn=Users,dc=we,dc=dirsrv,dc=com.>
Which doesn't make sense, because search base and attribute are flipped in this case. Might just be a coding issue with how they are displaying the log message (switched variables).
Either way, there ARE entries under that base with cn attribute. So it doesn't make sense.
The error message is garbled, but it is just the way it's displayed (it looks like it's being addressed in a later version). I'm running out of ideas here (perhaps this could be raised as an SR), a last idea is to check that the oamadmin user exists under your user searchbase.
Thanks. I have an open SR on this issue, but haven't made much progress.
The below parameter values are case sensitive, change these values to lowercase and try.
Got any replies yet? I am also facing the exact same issue.