-
1. Re: <security-enabled>true</security-enabled> in messaging subsystem not working in JBOSS Wildfly.
jbertram Sep 2, 2015 12:48 PM (in response to vinothkumarj7)What does your client look like?
Typically you would just use the "add-user" script in the bin directory to create the proper user and add it to the appropriate group. Once that's done it's up to the client to send the proper credentials when it connects (via the JMS API).
-
2. Re: <security-enabled>true</security-enabled> in messaging subsystem not working in JBOSS Wildfly.
vinothkumarj7 Sep 3, 2015 1:08 AM (in response to jbertram)Hashtable props = new Hashtable();
props.put(Context.INITIAL_CONTEXT_FACTORY,"org.jboss.naming.remote.client.InitialContextFactory");
props.put(Context.PROVIDER_URL, "remote://"+args[0]+":4447");
props.put(Context.SECURITY_CREDENTIALS,"admin");
props.put(Context.SECURITY_PRINCIPAL,"admin");
This is the client side credentials I use to connect via JMS API.
-
3. Re: <security-enabled>true</security-enabled> in messaging subsystem not working in JBOSS Wildfly.
jbertram Sep 3, 2015 9:28 AM (in response to vinothkumarj7)I assume this is the only place where you're passing the username and password. If that's true then it explains why you're receiving the security exception because this Hashtable of properties only applies to the JNDI lookup and not the actual JMS connection. You should be passing the username and password as part of the call to javax.jms.ConnectionFactory.createConnection(String username, String password).