Bug 31070 - Mark school OUs with special objectClass
Mark school OUs with special objectClass
Status: RESOLVED DUPLICATE of bug 31407
Product: UCS@school
Classification: Unclassified
Component: LDAP
UCS@school 3.1
Other Linux
: P2 enhancement (vote)
: UCS@school 3.x
Assigned To: Bugzilla Mailingliste
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-04-16 10:39 CEST by Alexander Kläser
Modified: 2013-05-31 13:36 CEST (History)
1 user (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): Cleanup, Further conceptual development
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-04-16 10:39:36 CEST
The current handling of school OUs is erroneous as an OU can not easily be identified as representing a school OU. Another problem are currently OUs that do not reside directly below the LDAP base (e.g., district mode).

An easy solution to this problem is a special objectClass that is attached to the school OU. This would solve many related problems. Through this, school ID and school name (as shown to the user) could also be separated.
Comment 1 Alexander Kläser univentionstaff 2013-05-31 13:36:31 CEST
Such an object class already exists: ucsschoolOrganizationalUnit

There already exists a patch (in Bug 30251, see also Bug 31407) that implements this idea.

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