#1380 winsync doesn't sync the employeeType attribute when it is changed in AD and you have specified a default value
Closed: wontfix 5 years ago Opened 12 years ago by rmeggins.

If you use ipaWinSyncUserAttr to provide a default value for employeeType e.g.

ipaWinSyncUserAttr: employeeType unknown

then change employeeType in AD, the value in ipa is always "unknown". The user is added from AD with employeeType missing in AD, and ipa fills in the value "unknown". But when the user is modified in AD to change the employeeType, the new value should replace "unknown".


Trying to reproduce this issue. How do you update employeeType in AD? If I add a user as a New User or New InetOrgPerson, I don't see a field that corresponds to employeeType. I'm going to try a field that is always present like Job Title to see if that breaks.

If nobody else is able to test it, I'm setting up winsync test on my VMs. Taking over this ticket temporarily and will return it to rmeggins if there is something on 389-ds side.

Move to 3.0 Core Effort after discussing with Rob and the team.

Moving the ticket to the next month iteration.

Rich, I think we have issue here -- as reproduced by shanks, the 'employeeType unknown' does not change to the new value set at AD side. It looks like ipa-winsync.c does not include these newly created attributes into consideration next time they are updated.

Replying to [comment:8 abbra]:

Rich, I think we have issue here -- as reproduced by shanks, the 'employeeType unknown' does not change to the new value set at AD side. It looks like ipa-winsync.c does not include these newly created attributes into consideration next time they are updated.

Please provide me with the exact steps to reproduce the problem. I've tried before and could not reproduce.

Metadata Update from @rmeggins:
- Issue assigned to rmeggins
- Issue set to the milestone: Tickets Deferred

7 years ago

Thank you taking time to submit this request for FreeIPA. Unfortunately this bug was not given a priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfil this request I am closing the issue as wontfix. To request re-consideration of this decision please reopen this issue and provide additional technical details about its importance to you.

Metadata Update from @rcritten:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata