[
https://issues.jboss.org/browse/WFLY-3288?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-3288:
----------------------------------------
For anyone looking into this, re: using the CLI for this functionality, that's fine so
long as it does not create a requirement for the CLI to have access to the server
filesystem. We already made that mistake with the "module" commands in the CLI.
It's even possible we could relax my constraint above re: CLI access to the server
filesystem, but that will need to be done as part of general change with a broader
discussion so we can iron out how to make it clear to users what the semantics are.
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