Bug 38447 - Describe how to configure different default basedn for additional connector
Describe how to configure different default basedn for additional connector
Status: RESOLVED WONTFIX
Product: UCS manual
Classification: Unclassified
Component: Services for Windows
unspecified
Other Linux
: P5 normal (vote)
: UCS 4.0-x
Assigned To: Docu maintainers
Samba maintainers
:
Depends on: 5407
Blocks:
  Show dependency treegraph
 
Reported: 2015-05-06 11:25 CEST by Tim Petersen
Modified: 2024-04-17 13:16 CEST (History)
1 user (show)

See Also:
What kind of report is it?: ---
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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
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 Tim Petersen univentionstaff 2015-05-06 11:25:14 CEST
http://docs.univention.de/windows-4.0.html#ad

I thnk its okay that the configration of an additional connector isn't described here in detail. Nevertheless it should at least show how (or where) to specify the different default base dn:

"One OU (organisational unit) can be defined in LDAP for each AD domain, under which the objects of the respective domains are synchronised."
Comment 1 Tim Petersen univentionstaff 2015-05-07 07:49:02 CEST
At least this doesn't seem to be implemented - see Bug #5407.

Perhaps this should be clarified in the manual instead.
Comment 2 Nico Gulden univentionstaff 2024-04-17 13:16:46 CEST
This bug hasn't seen any update for several years. I close it.

If you still see a need for it, you can reopen the bug. Please add an argumentation about why it's important to take care of it.