Bug 985978

Summary:	Deleting the admin user causes Foreman orchestration errors
Product:	Red Hat Satellite	Reporter:	Mike McCune <mmccune>
Component:	Content Management	Assignee:	Ivan Necas <inecas>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	Nightly	CC:	dcleal, ehelms, omaciel
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-20 11:38:36 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 Mike McCune 2013-07-18 16:18:17 UTC

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 16:40:51 UTC

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 11:38:36 UTC


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