LocalUserClient missing from jboss-client.jar

29 views
Skip to first unread message

Daniel.Ger

unread,
Sep 21, 2023, 12:48:55 PM9/21/23
to WildFly
Hi everyone,
I noticed that the jboss-client.jar since I think two versions ago doesn't include the LocalUserClient anymore (package org.wildfly.security.sasl.localuser is missing).
Do you know if that was on purpose and if there is any other way how I should nowadays do the local user authentication?
For now, I'm just using the jboss-client.jar of an old version of Wildfly, which is still working with the most recent versions of the servier - but of course that's not a very good long term solution.
Any other ideas how to do it? 
Unfortunately I didn't find any documentation about this change, although I might just be bad at searching.

cf...@redhat.com

unread,
Sep 21, 2023, 1:03:20 PM9/21/23
to WildFly
It looks like an oversight to not including this class or wildfly-elytron-sasl-localuser.jar. To workaround this, you can append jboss-cli-client.jar (in the same directory as jboss-client.jar under WildFly installation) to your client classpath. Or you can directly append an appropriate version of wildfly-elytron-sasl-localuser.jar to your client path.

A better approach is to use BOM in your application's maven dependency management, such as wildfly-ejb-client-bom.

Daniel.Ger

unread,
Sep 21, 2023, 1:31:20 PM9/21/23
to WildFly
Thanks for the quick response!
We'll add the libraries. I've tested and it works perfectly with the jboss-cli-client.jar added, as well as with the BOM dependencies instead of the other jars.

Reply all
Reply to author
Forward
0 new messages