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
Alias: None
Product: RHQ Project
Classification: Other
Component: Core Server   
(Show other bugs)
Version: 1.3.1
Hardware: All Linux
medium vote
Target Milestone: ---
: ---
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-27 15:28 UTC by dsteigne
Modified: 2018-10-27 16:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-05-29 18:14:09 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 588822 None None None Never

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:
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.

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