none
How to Provision contact Objects RRS feed

  • Question

  • Hi ,

    I have created custom object type in FIM portal as "Contact" and in Metaverse as well. Mapping AD contact type object with my custom object I have successfully imported these contact objects in FIM portal.

    I have created MPR and workflow to provisioning contact type object in AD and I am using following attributes for Contact provisioning in from FIM portal to AD in my outbound sync rule

    When I run export to provisionion the contact created at FIM portal with above attributes then I get following error :

    I think I am missing some attribute that are necessary for Contact provisioning .... 

    Thanks

    Shivam Singh


    • Edited by Shivam P Singh Saturday, August 16, 2014 8:19 AM spelling mistake
    Saturday, August 16, 2014 8:17 AM

All replies

  • Could be the flow from displayName ==> cn. I'm pretty sure that updating the CN cannot be done this way.

    Could be mistaken, though. But try removing that flow

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    • Proposed as answer by kmittal82 Monday, September 1, 2014 8:48 AM
    Tuesday, August 26, 2014 6:47 PM
  • Hi Shivam,

    Check this link : http://technet.microsoft.com/en-us/library/dd379509(v=ws.10).aspx and let me know in case it was helpful.


    Regards,
    Manuj Khurana

    Wednesday, August 27, 2014 8:07 AM
  • Hi Soren,

    I removed the "cn" outbound attribute and then tried provisioning the contact object but No good. 

    Thanks for the suggestion.

    Wednesday, August 27, 2014 9:35 AM
  • Hello,

    delete the flow Display=>CN and verify that the MA account have the good right to manage the AD contact object. Let me know the result.

    Joris.


    Joris Faure

    • Proposed as answer by Joris FAURE Tuesday, January 20, 2015 12:18 AM
    Wednesday, August 27, 2014 3:42 PM
  • Haven't tried for contacts, but for users you need a persistent flow AND an initial flow for DN.


    Mike Crowley | MVP
    My Blog -- Planet Technologies

    Wednesday, August 27, 2014 11:42 PM
  • Do you have anything in the Event Log that could help? Also, could you maybe post your Pending Export values (before running the export)? The error 8311 indicates that you're maybe trying to put some illegal values into some of the attributes in AD.

    Regards, Soren Granfeldt
    blog is at http://blog.goverco.com | facebook https://www.facebook.com/TheIdentityManagementExplorer | twitter at https://twitter.com/#!/MrGranfeldt

    Saturday, August 30, 2014 5:55 AM
  • Haven't tried for contacts, but for users you need a persistent flow AND an initial flow for DN.


    Mike Crowley | MVP
    My Blog -- Planet Technologies

    I might be wrong, but I don't think both are needed - only the initial flow is mandatory. The persistent flow is needed if you wish to support renames of the AD object. 
    Monday, September 1, 2014 8:48 AM
  • Hi Soren,

    I removed the "cn" outbound attribute and then tried provisioning the contact object but No good. 

    Thanks for the suggestion.

    Just to be perfectly safe, can you try creating a new contact object after making this change? Also, make sure to import the new SR and do a full sync.
    Monday, September 1, 2014 8:50 AM