Bug 51289 - create_ou + create_dc do not check dc name length
create_ou + create_dc do not check dc name length
Status: RESOLVED DUPLICATE of bug 51274
Product: UCS@school
Classification: Unclassified
Component: Import scripts
UCS@school 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: UCS@school maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-05-14 16:29 CEST by Sönke Schwardt-Krummrich
Modified: 2020-05-14 17:39 CEST (History)
0 users

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 3: Will affect average number of 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?:
School Customer affected?: Yes
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 Sönke Schwardt-Krummrich univentionstaff 2020-05-14 16:29:47 CEST
When creating a new school via the UMC, the name of the new school server is automatically checked. This name must not exceed 12 characters in the UMC.

The CLI scripts create_ou and create_dc do not check the names of the school servers, which is why a customer has already completely incorrectly provisioned his domain and now had to correct this.
→ the scripts should throw an error if this is tried. In addition, there should be a parameter/UCR variable to disable this limitation if necessary.

The reason for the length restriction is generally the Windows clients, which may otherwise shorten the host names and cause login problems. The UCS manual states that the maximum length should be 13 characters (I have currently no idea, why the UMC module is limited to 12 characters for the school name).
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2020-05-14 17:39:55 CEST

*** This bug has been marked as a duplicate of bug 51274 ***