Bug 596838 – support JON having read-only access to the systems it manages

Bug 596838 - support JON having read-only access to the systems it manages

Summary:	support JON having read-only access to the systems it manages

Status:	CLOSED WONTFIX

Aliases:	None

Product:	RHQ Project
Classification:	Other
Component:	Core Server (Show other bugs)
Sub Component:
Version:	1.3.1
Hardware:	All Linux

Priority	low Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	RHQ Project Maintainer
QA Contact:	Mike Foley
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2010-05-27 11:28 EDT by dsteigne
Modified:	2014-05-29 14:14 EDT (History)
CC List:	2 users (show)

See Also:	https://bugzilla.redhat.com/show_bug.cgi?id=588822
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2014-05-29 14:14:09 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description dsteigne 2010-05-27 11:28:42 EDT

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 12:53:23 EDT

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.

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