| Summary: | ipa permission-mod prompts for all parameters | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Namita Soman <nsoman> |
| Component: | ipa | Assignee: | Rob Crittenden <rcritten> |
| Status: | CLOSED ERRATA | QA Contact: | Namita Soman <nsoman> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2 | CC: | jgalipea, mkosek |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | ipa-3.0.0-1.el6 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-02-21 09:09:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Namita Soman
2012-01-18 16:47:11 UTC
Upstream ticket: https://fedorahosted.org/freeipa/ticket/2280 When modifying a permission, I suspect, the target cannot be changed. So for example, if a permission was added with --subtree=cn=computers,cn=accounts,dc=testrelm, it cannot be edited to now be type=host If such changes are not valid, expecting a command switching target will throw an error. # ipa permission-add ManageHost --permissions=read --subtree=cn=computers,cn=accounts,dc=testrelm # ipa permission-add ManageHost --permissions=read --type=host should throw error- ipa: ERROR: invalid 'target': type, filter, subtree and targetgroup are mutually exclusive or some error indicating target cannot be switched. is that correct expectation? Or can target be changed? subtree is just a more generic way of defining type. --type just predefines some existing containers that IPA creates. Fixed upstream: master: https://fedorahosted.org/freeipa/changeset/677ea8cbfab8aadbd89ca479ed4453776f65fd30 Verified using ipa-server-3.0.0-20.el6.x86_64 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [ LOG ] :: ipa-permission-cli-1060 - modify permission --rename (bug 805478 and Bug 782847) :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: [10:26:03] :: Executing: ipa permission-mod APermission --rename=ABCPermission --------------------------------- Modified permission "APermission" --------------------------------- Permission name: ABCPermission Permissions: write Type: user :: [10:26:05] :: Modified permission APermission successfully :: [ PASS ] :: Running 'modifyPermission "APermission" rename ABCPermission' :: [10:26:05] :: Executing: ipa permission-show --all "ABCPermission" > /tmp/tmp.nqBo9qpHMv/permissionshow.out Permission name: ABCPermission :: [10:26:06] :: ipa permission ABCPermission Verification successful: Value of Permission name: = ABCPermission :: [ PASS ] :: Verify Permissions Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0528.html |