Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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.

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