First Last Prev Next    This bug is not in your last search results.
Bug 35227 - extend configurable "default container" settings for non-standard UDM objects
extend configurable "default container" settings for non-standard UDM objects
Status: RESOLVED DUPLICATE of bug 33969
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 3.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-07-01 14:47 CEST by Ingo Steuwer
Modified: 2018-04-13 13:29 CEST (History)
2 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
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 Ingo Steuwer univentionstaff 2014-07-01 14:47:32 CEST 
currently the "default container" (list of containers propmted in UMC during creation of new objects in UDM wizards) is configurable only for default UDM objects.

Extensions introducing their own UDM objects should be able to be configurable in this way, too:
- add extended attributes to the "default containers" object
- define which attribute to use per UDM object

AFAIK currently getDefaultContainer(lo, module) in config.py contains a static list of UDM objects and their default container LDAP attribute, UDM objects can only define a hardcoded list (variable "default_container").
Comment 1 Moritz Muehlenhoff univentionstaff 2014-07-01 15:04:50 CEST 

*** This bug has been marked as a duplicate of bug 33969 ***
First Last Prev Next    This bug is not in your last search results.