aux class attributes in LDAP driver (eDir to OID)?


eDir to OID via LDAP.

We have extended schema/aux class attributes, as does OID

I believe, because they're aux class attributes, we don't (or can't) put
them into the schema mapping policy?

And:

How to do a matching policy based upon the aux class attribute?


--
kjhurni
------------------------------------------------------------------------
kjhurni's Profile: https://forums.netiq.com/member.php?userid=322
View this thread: https://forums.netiq.com/showthread.php?t=48533

Parents
  • Hello,

    Account sync process among IDM and backend LDAP do not work as expected. When IDM pushes and update onto a record making it active / in-active a custom attribute is getting populated. Need to know where and how that being handled in IDM. 

    userAPP / designer / iManager ???

    Inputs appreciated !

    Sri

Reply
  • Hello,

    Account sync process among IDM and backend LDAP do not work as expected. When IDM pushes and update onto a record making it active / in-active a custom attribute is getting populated. Need to know where and how that being handled in IDM. 

    userAPP / designer / iManager ???

    Inputs appreciated !

    Sri

Children
  • Tagging onto an existing thread with a different question but vaguely related may not be super helpful in terms of getting responses.

    However, this is likely a driver issue.

    That you ask the question "userAPP / designer / iManager?" makes me think you are not super familiar with this.

    Take care in actions you take until you understand what you are doing. (Very easy to break things as an Admin...)

    Do you know how to find the engine trace?  Do you know how to read it?  Look for the trace file for the LDAP driver of interest, generate this test case, and search the trace to find the event.

    Open a new thread and post the trace into the message and we can try to help you.