Bug 45582 – LDB module univention_samaccountname_ldap_check should allow creating users

Bug 45582 - LDB module univention_samaccountname_ldap_check should allow creating users


Summary:	LDB module univention_samaccountname_ldap_check should allow creating users

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Samba 4
Version:	UCS@school 4.2
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:	31936
	Show dependency tree / graph

Reported:	2017-10-24 11:29 CEST by Arvid Requate
Modified:	2020-07-14 11:21 CEST (History)
CC List:	3 users (show)

See Also:	47954
What kind of report is it?:	Feature Request
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	2: Will only affect a few 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?:
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 Arvid Requate

2017-10-24 11:29:19 CEST

The LDB Module univention_samaccountname_ldap_check should allow creating users. 

It's task is to ensure the uniqueness of account names and allocate a SID, not to enforce other restrictions based on account types.


This would help for Bug 31936.

+++ This bug was initially created as a clone of Bug #31936 +++

Comment 1 Michel Smidt 2020-07-14 11:21:23 CEST

This issue has been filed against UCS@school 4.2.

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

If this issue still occurs in newer UCS@school versions, please reopen it and update the UCS@school version. In this case please provide detailed information on how this issue is affecting you.