Bug 985978 - Deleting the admin user causes Foreman orchestration errors
Deleting the admin user causes Foreman orchestration errors
Status: CLOSED DUPLICATE of bug 868910
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Content Management (Show other bugs)
Nightly
Unspecified Unspecified
unspecified Severity high (vote)
: Unspecified
: --
Assigned To: Ivan Necas
Katello QA List
: Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-18 12:18 EDT by Mike McCune
Modified: 2014-05-20 07:38 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-05-20 07:38:36 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike McCune 2013-07-18 12:18:17 EDT
If you try to delete the default 'admin' user created during installation it will fail with either a:

 * Failed to perform additional action KatelloForemanEngine::Actions::UserDestroy: 422 Unprocessable Entity

or 

 *  Failed to perform additional action KatelloForemanEngine::Actions::UserDestroy: 403 Forbidden

We need to allow deleting of any user without error as long as the rules are maintained to have an existing user with Administrator rights within the database.
Comment 1 Dominic Cleal 2013-07-18 12:40:51 EDT
Foreman requires an admin user that it uses for various anonymous actions, e.g. Puppet report uploads, hosts updating their build state and when logins are disabled.  I'm not sure that having this fall back to another user that happens to have admin right would be desirable either, so I'd suggest we still need some sort of anonymous admin user by default for automated actions.

It would make sense though to only allow user-defined users to be able to log in and to have the anonymous admin account locked and unusable.
Comment 3 Dominic Cleal 2014-05-20 07:38:36 EDT

*** This bug has been marked as a duplicate of bug 868910 ***

Note You need to log in before you can comment on or make changes to this bug.