This content has been marked as final. Show 8 replies
It looks more like a basepoint issue.
Or for these accounts the GUID recorded in IDM do not match the SID in AD.
You could edit one user in the debug interface and test removing the attribute accountGUID in the ResourceInfo element.
Then does this problem still occur?
Thanks for your reply.
I have tried removing the accountId from resourceIno. But when the user is updated again it still throws the same 'Account not found in AD'.
What do you think the root cause for this? Should we also upgrade IDM product along with connector?
Did you remove accountId instead of accountGUID ?
I am not seeing an accountGuid in resource info. It contains an accountId and tempId. Should it aslo has accountGuid?
Edited by: 907551 on Aug 13, 2012 11:25 AM
The GUID is an alternative identifier used to locate an account, even when the account has been renamed.
In case of mismatch I already had the symptoms you described.
I thought it was used for AD.
Other than that or a basepoint/filter misconfiguration, I don't see what can be causing this.
There are defects fixed in the AD connector that also required a comparable code change on the OW side too. This is part of why you must use the connector that comes with the version of OW you're running. I would strongly recommend that you upgrade OW as well.
If you still experience problems I would then test 18.104.22.168 and the AD connector that comes with it.
Hope this helps.
Thanks let me try this.