Bug 41689 – Consider respecting Active Directory Name Length Limits

Bug 41689 - Consider respecting Active Directory Name Length Limits


Summary:	Consider respecting Active Directory Name Length Limits

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	General
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 enhancement with 2 votes (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-06-28 15:29 CEST by Michael Grandjean
Modified:	2019-01-03 07:23 CET (History)
CC List:	1 user (show)

See Also:	30023 15112 42904
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?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Grandjean

2016-06-28 15:29:50 CEST

Microsoft Active Directory implements some name length limits (https://technet.microsoft.com/de-de/library/active-directory-maximum-limits-scalability(v=ws.10).aspx#BKMK_NameLimits) that are more restrictive than what UCS allows. For example, common names are limited to 64 characters. 

UCS and Samba allow common names that are longer than 64 characers:

> cn: DiesisteinGruppennamemitsehrvielenZeichenumdasLimitzutestenUndzuueberschreiten
> sAMAccountName: DiesisteinGruppennamemitsehrvielenZeichenumdasLimitzutestenUndzuueberschreiten

Tbh, I consider this an advantage over MS Active Directory, but we might face problems when it comes to interoperability (AD Connector, AD Trusts, 3rd party applications ...)

Maybe we should implement checks / warnings, maybe depending on the installed Apps?

Comment 1 Stefan Gohmann

2019-01-03 07:23:07 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.