Bug 1070227

Summary: Enable JON Agent to manage resources which belong to a different usergroup/userid
Product: [JBoss] JBoss Operations Network Reporter: Heiko W. Rupp <hrupp>
Component: Agent, Plugin ContainerAssignee: Thomas Segismont <tsegismo>
Status: CLOSED WONTFIX QA Contact: Mike Foley <mfoley>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: JON 3.3.0CC: hrupp, jshaughn, myarboro, tsegismo
Target Milestone: ---   
Target Release: JON 3.3.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-09 13:11:49 UTC Type: Enhancement
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Heiko W. Rupp 2014-02-26 12:42:42 UTC 
For the JBoss ON agent to effectively manage resources it must be run under a specific operating system account and group which has access to all managed resources on the host machine the agent is running. However, if security practices or requirements state that each service (JBoss server or any other managed resource) must run under its own account, it can complicate file system and process permissions and even can event prevent the JBoss ON agent from managing or monitoring key resources such as a JBoss EAP server.