Bug 1476843
Summary: | User cannot edit own taxonomies | ||
---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Tomer Brisker <tbrisker> |
Component: | Users & Roles | Assignee: | Tomer Brisker <tbrisker> |
Status: | CLOSED ERRATA | QA Contact: | jcallaha |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 6.2.10 | CC: | bbuckingham, bkearney, cwelton, dhlavacd, dlezzoum, jcallaha, lpramuk, lzap, mhulan, mmccune, tbrisker, zhunting |
Target Milestone: | Unspecified | Keywords: | FieldEngineering, Reopened, Triaged |
Target Release: | Unused | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | foreman-1.11.0.89-1 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-21 20:16:43 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Tomer Brisker
2017-07-31 15:06:19 UTC
Even simpler reproducer: 1. Log in as admin 2. Try to edit own taxonomies (add/remove a location/organization on your account) 3. Save You will see the save succeed, but going into editing account again you will see the change was not preserved. Hi Bryan, This scenario is not automated, opened an issue for that https://github.com/SatelliteQE/robottelo/issues/5228 Verified in Satellite 6.2.15 Snap 2. Created a new organization and location. Edited the main admin account to align them. Saved the config. Reloaded the edit user page for the admin account. The orgs and locations were aligned correctly. Created a new account with admin privileges and no orgs or locations aligned. Signed in to the new account, being presented with the edit user page. Aligned the new org and default location to the user. After logging back in to the test user, the new org and default location were aligned correctly. 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. https://access.redhat.com/errata/RHBA-2018:1672 This comment was flagged a spam, view the edit history to see the original text if required. This comment was flagged a spam, view the edit history to see the original text if required. |