-
1. Re: Stopping JBoss 7 through CLI
fabrizio.benedetti Oct 7, 2011 5:39 AM (in response to semubiz)I found same issue.
I solved with a workaround, disabling security-realm in native-interface and setting management interface's inet-address to "localhost".
My standalone.xml looks like:
...
<management>
<security-realms>
<security-realm name="PropertiesMgmtSecurityRealm">
<authentication>
<properties path="mgmt-users.properties" relative-to="jboss.server.config.dir"/>
</authentication>
</security-realm>
</security-realms>
<management-interfaces>
<native-interface interface="management" port="9999"/>
<http-interface interface="public" port="9990" security-realm="PropertiesMgmtSecurityRealm"/>
</management-interfaces>
</management>
...
<interfaces>
<interface name="management">
<inet-address value="localhost"/>
</interface>
<interface name="public">
<inet-address value="192.168.1.1"/>
</interface>
</interfaces>
...
It is a problem only if you want to launch you script remotely.
-
2. Re: Stopping JBoss 7 through CLI
rhusar Oct 7, 2011 5:49 AM (in response to semubiz)Hi guys,
that surely needs improving, here is a Jira for it:
https://issues.jboss.org/browse/AS7-2036
Fabrizio that is a hack, but nice workaround :-)
Thanks,
Rado
-
3. Re: Stopping JBoss 7 through CLI
dlofthouse Oct 7, 2011 6:08 AM (in response to rhusar)I have scheduled the issue - we will get support for specifying the username and password added.
-
4. Re: Stopping JBoss 7 through CLI
rhusar Oct 7, 2011 6:26 AM (in response to dlofthouse)Thanks Darran.
-
5. Re: Stopping JBoss 7 through CLI
semubiz Oct 7, 2011 6:52 AM (in response to dlofthouse)Thanks for your replies. As there is no support currently I'll go with Fabrizio's suggestion.
-
6. Re: Stopping JBoss 7 through CLI
dlofthouse Oct 10, 2011 2:54 PM (in response to semubiz)Just a quick update.
I am just running the changes past the lead for the CLI so the changed can be added to the repo but for the scenarios described in this thread I have now added support for the username and password to be specified on the command line and if authentication is required and the values have not been set the users will be prompted to supply the missing values.
-
7. Re: Stopping JBoss 7 through CLI
chrishiner Oct 11, 2011 9:09 AM (in response to dlofthouse)Would it make sense to have an option to specify a file with credentials in it, so they don't have to be passed on the command line?
I worked around the lack of username/password options with an Expect script, but that's overkill for most things.
-
8. Re: Stopping JBoss 7 through CLI
dlofthouse Oct 11, 2011 9:44 AM (in response to chrishiner)That could also be an option although at this stage I think that would be more likely if it was contributed from the community.
My next tasks are to look at some of the non-password based authentication mechanisms for our management interfaces so those will also become alternatives to needing to pass in a username and password on the command line.
-
9. Re: Stopping JBoss 7 through CLI
rhusar Oct 11, 2011 10:19 AM (in response to chrishiner)Chris Hiner wrote:
Would it make sense to have an option to specify a file with credentials in it, so they don't have to be passed on the command line?
I worked around the lack of username/password options with an Expect script, but that's overkill for most things.
Hey Chris, here is a Jira for it:
https://issues.jboss.org/browse/AS7-2072
As Darran says, feel free to take it on if you would dare ;-)
-
10. Re: Stopping JBoss 7 through CLI
chrishiner Oct 11, 2011 1:02 PM (in response to rhusar)I think I'll wait and see what Darran comes up with. Non-password based authentication mechanisms sounds like an even better answer for future use.