Hello,

Looking for ideas here.  I have a simple HR, Portal, AD setup.  The HR and AD synchronization rules are defined in the portal.

I have no trouble loading the HR data into the HR CS and subsequent sync in the metaverse.  I have no trouble exporting the accounts to AD. 

My issue surrounds getting the users into the portal.  Here's the scenario:

Full Sync indicates 190 Provisioning adds (190 users)

Subsequent Full Export Adds 190, each of them in an "Awaiting Export Conformation" status.

A subsequent full import (an attempt to confirm the export) indicates 190 deletes (the same ones I'm trying to add).

So, I'm missing something here.  The Domain, Object SId and Account Name attributes, among others are being flowed.

Any ideas?

Thanks in advance,

Greg

Seems like an MPR is deleting all the accounts created.  Do you have any custom MPRs in the portal that would delete al newly created users??

Hello.

In your synchronization rule ( i guess hr import rule), have you marked the checkbox under "relationship" for create resource in FIM? 

/T

Looks like users are created and deleted in portal!

Check requests in portal and see if there are delete person logs.

Tobias,

Yeah, I checked the "Create resource in FIM" check box.  The HR import works great.  The user account flow from HR into FIM and out to AD. 

Nosh,

I might be onto something, here.  I suspected the same thing.  I'm still digging into this, but he MVObjectId in CS and the MVObjectId in the MV are different (I think - still verifying).  I'm beginning to think it's some kind of join logic that's not right.  It's doesn't seem as if the MA is properly locating an existing object in the MV. I can't define join and projection rules in the FIMMA, so I'm trying to figure out what that MA is using for an existence test. 

Still looking.

Hi Greg,

What do you have in the FIM Portal requests ?

Do you see the creation of users?

Regards,