This may be verging more on a forum question issue than a dev list
discussion but at the moment I can not reproduce what you are saying for
the username/password based authentication issue.
Clean builds of both wildfly-core and wildfly and I am able to connect
using the CLI with that command once I have defined an admin user.
Regards,
Darran Lofthouse.
On 19/08/14 05:37, Claudio Miranda wrote:
Hi, just updated to latest in wildfly repo, started standalone and
tried to connect with an username, it fails
./jboss-cli.sh -c --user=admin
SaslException: Authentication failed: the server presented no
authentication mechanisms
It works with local authentication
./jboss-cli.sh -c
Users admin is added as
./add-user.sh -u admin -p admin123@
Also, it fails with ssl in management interface.
Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect
to https-remoting://localhost:9993. The connection failed
at
org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:118)
at
org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:257)
at
...
Caused by: java.nio.channels.ClosedChannelException
I configured ssl as described in [1]
1.
http://claudius.com.br/2014/08/protect-wildfly-management-interface/