These are the properties:
The login.conf file, pointed to by ?java.security.auth.login.config?, needs to contain:
Your remote application needs to authenticate before making any EJB (delegate) calls. This is the code:
LoginContext lc = new LoginContext( "jboss_client", new TextCallbackHandler() );
The TextCallbackHandler is an example that prompts for credentials from the console. Your app may instead opt to implement a custom callbackhandler that gets credentials by some other means?depends on requirements.
There is a reason for this:
the java:comp/env namespace is reserved for application components running in a managed environment. What this basically means is that each application component has its own private namespace bound to the context of
When running outside of the container, this does not work because the thin Java client does not have access to such a namespace. In this scenario, you would use the JNDI name directly, or develop an Application client that does have a java:comp/env namespace.
Use the global JNDI namespace in JBoss. Don't bind to java:/