Symantec IGA

  • 1.  In-Bound Sync issue

    Posted Apr 21, 2017 10:32 AM

    Right now we are facing issue with Inbound Sync. If we create the User in AD and Run the Explorer correlate then User is getting created in PD but not getting create in UserStore. At Notify Log , i'm getting some error messages..

     

    -------------error-----------

    =================================================
    20170421:151329:TID=bfbb70:I: START: Notify Batch Processing
    20170421:151329:TID=bfbb70:I: Sending Notification: eTNotifyOpID=950f08f6-887a-1036-82bf-8b7b8c8f9a2a
    20170421:151329:TID=bfbb70:I: Event: Modify_Global_User (eTGlobalUserName=moderm09)
    20170421:151329:TID=bfbb70:I: SeqNo: 0000000576
    20170421:151329:TID=bfbb70:I: Priority: 5
    20170421:151329:TID=bfbb70:I: Try sending payload to http://stagcmim1:8080/iam/im/ETACALLBACK/?env=frieslandcampina
    20170421:151329:TID=bfbb70:E: ERROR: This method requires the presence of an attribute which was not provided. The attribute is name
    20170421:151329:TID=bfbb70:E:+d uid.
    20170421:151329:TID=bfbb70:E: Error in notification processing: Reason: Operation failed. ERROR: IMS was not able to consume the not
    20170421:151329:TID=bfbb70:E:+ification successfully.
    20170421:151329:TID=bfbb70:E: Originated from: EtaNotifyTools.cpp [1148].
    20170421:151329:TID=bfbb70:I: DONE: Notifications Processed: 0/100+ [FAILED]
    20170421:152310:TID=00eb70:I: NOT SENDING NOTIFICATIONS: Unable to get IMS connectivity information. This prevents this Provisioning
    20170421:152310:TID=00eb70:I:+ Server from communicating with the corresponding Identity Manager Server
    20170421:152329:TID=bfbb70:I: =================================================
    20170421:152329:TID=bfbb70:I: START: Notify Batch Processing
    20170421:152329:TID=bfbb70:I: Sending Notification: eTNotifyOpID=950f08f6-887a-1036-82bf-8b7b8c8f9a2a
    20170421:152329:TID=bfbb70:I: Event: Modify_Global_User (eTGlobalUserName=moderm09)
    20170421:152329:TID=bfbb70:I: SeqNo: 0000000576
    20170421:152329:TID=bfbb70:I: Priority: 5
    20170421:152329:TID=bfbb70:I: Try sending payload to http://stagcmim1:8080/iam/im/ETACALLBACK/?env=frieslandcampina
    20170421:152329:TID=bfbb70:E: ERROR: This method requires the presence of an attribute which was not provided. The attribute is name
    20170421:152329:TID=bfbb70:E:+d uid.
    20170421:152329:TID=bfbb70:E: Error in notification processing: Reason: Operation failed. ERROR: IMS was not able to consume the not
    20170421:152329:TID=bfbb70:E:+ification successfully.
    20170421:152329:TID=bfbb70:E: Originated from: EtaNotifyTools.cpp [1148].
    20170421:152329:TID=bfbb70:I: DONE: Notifications Processed: 0/100+ [FAILED]

     

    -----------END------

     

     

    Any help on this issue. 



  • 2.  Re: In-Bound Sync issue

    Posted Apr 21, 2017 04:47 PM

    Hi hsingh.nitk

     

        Please be sure that you mapped all required fields to create a user in IM.    In your AD connector (the fields mapped to the provisioning server fields).  In the IM Management console (Management Console / Home > Environment > YourEnvironment > Advanced Settings > Provisioning)  check that the "Provisioning attribute"  required is assigned to a "User attribute".  Some times it helps to look in IM the task "Create user" in order to validate the required fields.

     

    Good luck!!!

     

    Efren



  • 3.  Re: In-Bound Sync issue
    Best Answer

    Posted Apr 24, 2017 09:54 AM

    During Explore/CorrelateCreate only the eTGlobalUserName and eTUserID will have values. So you should do the following:

    - In the IM UserDir XML relax the retriction so that additional fields are not required (you can leave required on the screen definition)

    - Either use a PX Policy of type=UI on Submission of the Provisioning Create User task to set initial values for any additional required fields, or on the screen definition associated with the Provisioning Create User task configure default values for the additional required fields.

    If you need further assistance I suggest opening a support case.



  • 4.  Re: In-Bound Sync issue

    Posted May 02, 2017 04:37 AM

    Thanks For your Valuable Ans..