Bug 715340

Summary:	Requesting ability to change the JAAS Realm JON uses to authenticate against jmx-console on per-server basis
Product:	[JBoss] JBoss Operations Network	Reporter:	dsteigne
Component:	Plugin -- JBoss EAP 4, Security, Plugin -- JBoss EAP 5	Assignee:	RHQ Project Maintainer <rhq-maint>
Status:	CLOSED WONTFIX	QA Contact:	Mike Foley <mfoley>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	JON 2.4.1	CC:	hrupp, jshaughn, myarboro
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	JON 3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-09-03 17:58:35 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

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.