Bug 41263 - Enhance AD Connector mapping with password sync for windows machine accounts
Enhance AD Connector mapping with password sync for windows machine accounts
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2016-05-11 22:13 CEST by Michael Grandjean
Modified: 2019-01-03 07:22 CET (History)
4 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Forked for project
Max CVSS v3 score:
best: Patch_Available+


Attachments
Add pw sync to windows computer objects (1.22 KB, text/plain)
2016-05-11 22:13 CEST, Michael Grandjean
Details
Add pw sync to windows computer objects v2 (1.26 KB, patch)
2016-05-11 22:33 CEST, Michael Grandjean
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2016-05-11 22:13:47 CEST
Created attachment 7656 [details]
Add pw sync to windows computer objects

A customer has the requirement to also sync the password hashes of the windows machine accounts to/from Windows AD. Right now the AD Connector only syncs the windows computer object without the password hash.

The attached patch will enable this feature via an additional UCRV.
Comment 1 Michael Grandjean univentionstaff 2016-05-11 22:33:26 CEST
Created attachment 7657 [details]
Add pw sync to windows computer objects v2

Sorry, the first patch was an old version. My bad.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:22:36 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.