Bug 30023 - limit attribute "company" to 64 chars to avoid conflicts with S4/AD
limit attribute "company" to 64 chars to avoid conflicts with S4/AD
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Users
UCS 3.1
Other Linux
: P3 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-14 13:49 CET by Ingo Steuwer
Modified: 2018-04-13 13:29 CEST (History)
3 users (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 Ingo Steuwer univentionstaff 2013-01-14 13:49:26 CET
reported in Ticket 2013010321000591

Samba4/AD allows only 64 characters in the attribute "company", UDM allows more. This can lead to rejects in the sync between OpenLDAP and Samba4 or AD.
Comment 1 Stefan Gohmann univentionstaff 2013-01-15 06:40:15 CET
This limit should be defined in the UDM modules. If it is a problem for a customer he should be able to overwrite the syntax via UCR.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:37:52 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 3 Stefan Gohmann univentionstaff 2017-08-08 07:09:53 CEST
This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly changed in later releases. Thus, this issue is now being closed.

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