Bug 715340 - Requesting ability to change the JAAS Realm JON uses to authenticate against jmx-console on per-server basis
Summary: Requesting ability to change the JAAS Realm JON uses to authenticate against ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Operations Network
Classification: JBoss
Component: Plugin -- JBoss EAP 4, Security, Plugin -- JBoss EAP 5
Version: JON 2.4.1
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: JON 3.3.0
Assignee: RHQ Project Maintainer
QA Contact: Mike Foley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-22 15:00 UTC by dsteigne
Modified: 2018-11-26 18:21 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-09-03 17:58:35 UTC
Type: Enhancement

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

Description dsteigne 2011-06-22 15:00:40 UTC 
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):
2.4.1

How reproducible:


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


Expected results:


Additional info:
Comment 1 Jay Shaughnessy 2014-09-03 17:58:35 UTC 

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.