Bug 33889 - Add ucr.userNameMapping method
Add ucr.userNameMapping method
Status: CLOSED INVALID
Product: UCS
Classification: Unclassified
Component: UCR
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-0-errata
Assigned To: Arvid Requate
Stefan Gohmann
:
Depends on: 33650
Blocks: 33893 33897
  Show dependency treegraph
 
Reported: 2014-01-09 18:25 CET by Arvid Requate
Modified: 2014-01-21 12:29 CET (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

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2014-01-09 18:25:18 CET
For univention-lib we need a ucr.userNameMapping analogous to the ucr.groupNameMapping introduced via Bug #33650.


+++ This bug was initially created as a clone of Bug #33650 +++
Comment 1 Arvid Requate univentionstaff 2014-01-13 20:20:31 CET
This bug will be set to resolved/fixed after testing with Bug 33644.

Advisory: 2013-12-09-univention-config-registry.yaml
Comment 2 Stefan Gohmann univentionstaff 2014-01-15 10:56:30 CET
Why is this part of python/univention/config_registry/backend.py? Wouldn't it be better to handle this in univention-lib only?
Comment 3 Arvid Requate univentionstaff 2014-01-15 12:49:34 CET
The userNameMapping method has been removed from univention-config-registry in favour of the custom_username function in python-univention-lib. univention-lib has been adjusted accordingly and this bug number has been removed from the advisory 2013-12-09-univention-config-registry.yaml.
Comment 4 Stefan Gohmann univentionstaff 2014-01-21 12:29:24 CET
OK
Comment 5 Stefan Gohmann univentionstaff 2014-01-21 12:29:36 CET
Nothing to release