[jboss-jira] [JBoss JIRA] (WFLY-3288) Update add-user to use AESH or move it into the CLI
[
https://issues.jboss.org/browse/WFLY-3288?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-3288:
----------------------------------------
Yes, that's possible. My main concern though is the CLI is a remote tool and one that
can manage a domain, so if it does something that won't work remotely or with a domain
it should not involve a random end user experience the way the current "module"
commands do.
If the regular management API would support updating these properties files, then the CLI
could just add high level wrappers over those low level ops. That would be great. But if
we *also* drop the existing add-user.sh scripts and only support the CLI, then the user
has to launch a server process (perhaps in --admin-only) in order to manipulate users.
That's annoying.
One thing I've been thinking about for this kind of problem is being able to launch an
embedded AS inside the CLI. This could handle any sort of initial configuration task. The
user instead of doing -c on the command line or "connect" in the shell uses
"embed" or something, with appropriate other params. The CLI launches an
embedded AS and connects via a non-remoting based interface. Thereafter the commands are
the same as if the server was remote.
Update add-user to use AESH or move it into the CLI
---------------------------------------------------
Key: WFLY-3288
URL: https://issues.jboss.org/browse/WFLY-3288
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Domain Management, Scripts
Reporter: Darran Lofthouse
Fix For: Awaiting Volunteers
Within the add-user utility it is difficult to handle situations where we do not have
access to a java.io.Console which is the easiest way to handle password reading without an
echo to the user e.g. in Cygwin
Switching to AESH would allow us to use the implementation there to handle this.
Alternatively it may actually make sense to make add-user a special mode of the CLI, we
may at some point want to switch to runtime operations being executed on the server so
porting to the CLI could be the first step to make this possible.
Overall this is going to require further discussion so the comments here are just a
starting point.
--
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