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):
Steps to Reproduce:
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.