You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, Team!
For map our domain uers we use People-objects in the Insight structure. We set up LDAP import users from AD, defined attributes. Import new people is working correctly, but we have some problems with updating "manager" attribute. If we change user Manager in AD and run sincronization, it will pass without updating the attribute Manager. And if we delete Manager from object, new manager was updated...
Insight-attribute "Manager" was configured as Manager - Object - People - Reference
And in importing attributes manager = Manager and Object mapping = "DN = ${manager}"
If we change attribute "userAccountControl", Object updating work successfully. But it not work for Manager :(
Hm, looks like you are using value type for mapping.
It seems to me that on import userAccountControl column value from file goes to Insight Attribute UserAccountControl but for mapping you are using Value Type which is UAC. This is okay as you said.
But for data locator manager where you want to update data for insight attribute Manager, you use mapping DN, and this is another Insight Attrribute. Right?
If your goal is to update atribute Manager on object with values from column manager, I think you could try with Label = ${manager}
This is a good idea, but we tried to substitute both SID and CN and others. And it does not work. It`s working only DN = ${manager}.
Now, I am change properties "Missing objects outbound references = Remove" and "Empty values = Remove" and all working!
Thank you, Ricky, for being with me in difficult times :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi. I'm trying to set up a similar ldap import, but I'm faced with the problem of filling in the Object mapping (IQL) field. When Data Locator and Insight Attribute are selected, it simply becomes unavailable for inputting values. How were you able to enter values in this field?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
ObejctMapping will not work with any attribute type. What is the attribute type for Manager on this specific ObjectType?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Alexey AbramovHi! If you need AD import like my Manager or UAC attributes, this mapping need use only for Objects. Manager atribute referenced with himself ObjecType, and for UAC I create new ObjectType with UAC Id`s.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I noticed that Match Identifier is set to Case Sensitive. Any chance your import values are case sensitive?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We using AD SID as Identifier (like "S-1-5-21-1715567821-789336058-682003330-586352") and this identifier never changes after creating domain user.
And field Match Identifier contains only "Case Sensitive" value
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.