Bug 596838

Summary:	support JON having read-only access to the systems it manages
Product:	[Other] RHQ Project	Reporter:	dsteigne
Component:	Core Server	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WONTFIX	QA Contact:	Mike Foley <mfoley>
Severity:	medium	Docs Contact:
Priority:	low
Version:	1.3.1	CC:	ccrouch, jshaughn
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-05-29 18:14:09 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description dsteigne 2010-05-27 15:28:42 UTC

Description of problem:

support JON having read-only access to the systems it manages, e.g. run as an OS user with read-only permissions, connect to JBAS/Tomcat as users which do not have rights to execute invoke operations.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Joseph Marques 2010-09-16 16:53:23 UTC

to my knowledge, this issue is NOT about JON authz on the server-side (creating a no-perm user with access to certain JBAS resources).  this is about implementing the JBAS/EAP management features in such a way that it takes action using a limited-security user on the remote OS, which is something we need to enhance in the JBAS/EAP plugin.