Red Hat Bugzilla – Bug 1266225
Multiple Manager Support
Last modified: 2016-07-19 14:01:10 EDT
Description of problem:
WebUI and command line support for multiple managers does not exist.
Need to add support for multiple managers at command line and use the correct widget in UI
Version-Release number of selected component (if applicable):
FreeIPA, version: 4.1.4
Steps to Reproduce:
1. Execute 'ipa user-mod foo --manager=aaa --manager=bbb'
1. Attempt to assign more than one manager to a user
ipa: ERROR: invalid 'manager': Only one value is allowed
No additional fields present to set/select managers
Command completes successfully showing modified user with multiple managers in list.
Prompt appears to allow selecting multiple managers from list similar to the group membership for users prompt.
Per freenode IRC discussion with users rcrit and ab editing the file at /usr/lib/python2.7/site-packages/ipalib/plugins/user.py in my environment and changing line 593 from manager? to manager* fixes the command line issue.
The WebUI should be using the association widget for managers that is the same as what is used with group membership selection for users.
Note: Manager attribute is already multi-valued in the schema.
Yes, 'manager' is multivalued but IPA framework treats it as a single-valued in the option definition. In addition, the option also treats the content as a string, not as a reference to another LDAP object like 'manager' attribute definition says, and uses two specialized methods to convert between DNs and rdn values.
This all does not give us a chance to reuse association widget. In fact, 'manager' is similar to 'managedby' we have in hosts and OTP tokens, only the attribute name is different.
Lets not discuss implementation. The discussion should be whether the field should be made multi-valued in UIs/API or not. Will clone the bug to upstream Trac.
CLI part implemented upstream:
457c9746709042e6f4f8f37a85ca8ad562962405 Allow multiple managers per user - CLI part
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.