Bug 715340 - Requesting ability to change the JAAS Realm JON uses to authenticate against jmx-console on per-server basis
Requesting ability to change the JAAS Realm JON uses to authenticate against ...
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 4, Security, Plugin -- JBoss EAP 5 (Show other bugs)
JON 2.4.1
Unspecified Unspecified
unspecified Severity low
: ---
: JON 3.3.0
Assigned To: RHQ Project Maintainer
Mike Foley
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2011-06-22 11:00 EDT by dsteigne
Modified: 2014-09-03 13:58 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-09-03 13:58:35 EDT
Type: Enhancement
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description dsteigne 2011-06-22 11:00:40 EDT
Description of problem:
When fetching information from managed servers' JMX consoles, JON automatically attempts to authenticate against the jmx-console JAAS realm. While it is possible to configure the actual credentials it uses (Server->Inventory->Connection->Principal/Credentials), it doesn't seem possible to configure the JAAS realm itself, at least through the UI.

Can the capability to configure this for any particular EAP server be added to JON. I.e. have JON authenticate against most servers using securityDomain=jmx-console, but also be able to change certain servers to use securityDomain=my-custom-security-domain

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

How reproducible:

Steps to Reproduce:
Actual results:

Expected results:

Additional info:
Comment 1 Jay Shaughnessy 2014-09-03 13:58:35 EDT

Closing due to low priority and inactivity.  Re-open and re-target as needed.

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