Bug 46874 - AD-Connector configuration - pwdhash sync with default user doesn't work
AD-Connector configuration - pwdhash sync with default user doesn't work
Status: CLOSED FIXED
Product: UCS manual
Classification: Unclassified
Component: General
unspecified
Other Linux
: P5 normal (vote)
: UCS 4.3
Assigned To: Stefan Gohmann
Felix Botner
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2018-04-23 17:56 CEST by Nico Stöckigt
Modified: 2019-02-14 12:12 CET (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.069
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2018042321000341
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Stöckigt univentionstaff 2018-04-23 17:56:33 CEST
In chapter http://docs.software-univention.de/handbuch-4.3.html#windows:ad:connector paragraph 3 is written that a default user is enough to sync in read-only mode. This is no longer true since we have cancel using the windows service and using RPCs instead.

------------------------------------------------------------
#german

- Im Feld Active Directory-Konto wird der Benutzer konfiguriert, der für den Zugriff auf das AD verwendet wird. Die Einstellung wird in der Univention Configuration Registry-Variable connector/ad/ldap/binddn gespeichert. Der Replikationsbenutzer muss im AD Mitglied der Gruppe Domänen-Admins sein. Synchronisiert der Connector nur lesend von AD zu UCS, kann auch ein Standardbenutzerkonto angegeben werden.

+ Im Feld Active Directory-Konto wird der Benutzer konfiguriert, der für den Zugriff auf das AD verwendet wird. Die Einstellung wird in der Univention Configuration Registry-Variable connector/ad/ldap/binddn gespeichert. Der Replikationsbenutzer muss im AD Mitglied der Gruppe Domänen-Admins sein.

------------------------------------------------------------
#english

- In the Active Directory account field, the user is configured which is used for the access on the AD. The setting is saved in the Univention Configuration Registry variable connector/ad/ldap/binddn. The replication user must be a member of the Domain Admins group in the AD. If the connector performs read only synchronization from AD to UCS, a standard user account can also be specified.

+ In the Active Directory account field, the user is configured which is used for the access on the AD. The setting is saved in the Univention Configuration Registry variable connector/ad/ldap/binddn. The replication user must be a member of the Domain Admins group in the AD.
Comment 2 Stefan Gohmann univentionstaff 2018-12-11 07:47:33 CET
I've changed the manual.

git.knut.univention.de:univention/ucs.git
   ebcea93813..d7ac38fd17  stefan/docu-cleanup -> stefan/docu-cleanup

Jenkins Build:
http://jenkins.knut.univention.de:8080/view/Doku/job/BuildDocBookBranch/43/artifact/webroot/handbuch-4.3.html#ad-connector:basicsetup
http://jenkins.knut.univention.de:8080/view/Doku/job/BuildDocBookBranch/43/artifact/webroot/manual-4.3.html#ad-connector:basicsetup

Please reopen the bug after the QA, so that I can merge it.
Comment 3 Felix Botner univentionstaff 2018-12-13 14:19:28 CET
OK
Comment 4 Stefan Gohmann univentionstaff 2019-01-15 07:15:19 CET
(In reply to Felix Botner from comment #3)
> OK

Merged to UCS 4.3-3 and UCS 4.4-0.
Comment 5 Stefan Gohmann univentionstaff 2019-01-15 07:15:35 CET
(In reply to Stefan Gohmann from comment #4)
> (In reply to Felix Botner from comment #3)
> > OK
> 
> Merged to UCS 4.3-3 and UCS 4.4-0.

→ Verified.
Comment 6 Philipp Hahn univentionstaff 2019-02-14 12:12:52 CET
[master] dd16110 Bug #46874,Bug #32277,Bug #36733,Bug #39556,Bug #40162,Bug #41684,Bug #34726,Bug #41305,Bug #36869: PUBLISH