Bug 41036 – Create user with uidNumber > 55000 breaks user creation

Bug 41036 - Create user with uidNumber > 55000 breaks user creation


Summary:	Create user with uidNumber > 55000 breaks user creation

Status:	RESOLVED DUPLICATE of bug 37085

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-04-12 12:28 CEST by Florian Best
Modified:	2016-04-12 13:22 CEST (History)
CC List:	0 users

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):	Error handling
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 Florian Best

2016-04-12 12:28:15 CEST

It is currently possible to create a user with uidNumber: 9999999999999999 via UMC. After creating this user it is not possible to create any other user anymore because the locking mechanism fails with:

Das LDAP-Objekt konnte nicht gespeichert werden: Exklusiver Zugriff nicht möglich. : Typ war uidNumber

You have to manually change the lock-object underneath of cn=uidNumber,cn=temporary,cn=univention to fix this.

Comment 1 Florian Best

2016-04-12 12:33:18 CEST

The limits in the allocators are, but we nowhere enforce them in the handlers:
uidNumber = [{'first': 1000, 'last': 55000}
gidNumber =  {'first': 65536, 'last': 1000000}

Comment 2 Florian Best

2016-04-12 13:22:52 CEST


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