[
https://issues.jboss.org/browse/JBIDE-15614?page=com.atlassian.jira.plugi...
]
Martin Malina edited comment on JBIDE-15614 at 10/15/13 4:12 AM:
-----------------------------------------------------------------
[~rawb], you're right, when I set up an admin user it then works.
But I checked again and for EAP 6.1.0 no user is needed to access JMX on a local server.
So something has changed in EAP 6.2. But I spoke to EAP QE and they say the <local>
is still set for the SecurityRealm, so things should work the same. And indeed,
jboss-cli.sh is still able to connect to a local running EAP 6.2 without any password.
So can you please check what changed here? It may even be a bug in EAP.
was (Author: mmalina):
Rob, is this a new thing with EAP 6.2 that the local filesystem authetication is no
longer on? Because I don't need to setup any users for EAP 6.1.0 and JMX connection
just works (on a local server that is).
It seems this is the case - even web admin console asks me for password now :-\
And yes, I just checked, and when I set up a user it works.
Rename EAP 6.1 server type to 6.1+, ensure runtime detection is
accurate
------------------------------------------------------------------------
Key: JBIDE-15614
URL:
https://issues.jboss.org/browse/JBIDE-15614
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection, server
Affects Versions: 4.1.0.Final
Environment: JBDS 7.0.0.GA
Reporter: Martin Malina
Assignee: Max Rydahl Andersen
Fix For: 4.1.1.Beta1
1. When you try to add EAP 6.2 using runtime detection, it detects it as EAP 6.0.
2. When trying to add EAP 6.2 manually, there is no type EAP 6.2
Let me know if you want subtasks for these two.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira