Bug 19109 - AD-Connector UMC Modul erkennt FQDN nicht als gültigen Wert an
AD-Connector UMC Modul erkennt FQDN nicht als gültigen Wert an
Product: UCS
Classification: Unclassified
Component: UMC - AD Connector
Other Linux
: P5 normal (vote)
: UCS 3.2
Assigned To: Erik Damrose
Stefan Gohmann
: interim-2
Depends on:
  Show dependency treegraph
Reported: 2010-07-27 10:26 CEST by Tim Petersen
Modified: 2013-11-19 06:43 CET (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:


Note You need to log in before you can comment on or make changes to this bug.
Description Tim Petersen univentionstaff 2010-07-27 10:26:03 CEST
Auf 2.4 master (aus trunk):

FQDN ist WIN-FR5JHASK7EC.windows2008.domain und wird nicht als gültiger Wert zum Erkennen der BasisDN angenommen.
Comment 1 Moritz Muehlenhoff univentionstaff 2013-05-31 10:44:28 CEST
We will not ship a UCS 3.1-2 release; the next UCS release will be UCS 3.2.

As such, this bug is moved to the new target milestone.
Comment 2 Erik Damrose univentionstaff 2013-08-27 13:01:10 CEST
I could not reproduce this behaviour with the current UCS 3.2 build. I have tested against a Win2012 AD Server and a Win2008 AD Server with the exact FQDN.

univention-ad-connector 8.0.0-2

-> WorksForMe
Comment 3 Stefan Gohmann univentionstaff 2013-09-19 15:32:00 CEST
Comment 4 Stefan Gohmann univentionstaff 2013-11-19 06:43:22 CET
UCS 3.2 has been released:

If this error occurs again, please use "Clone This Bug".