3 Replies Latest reply on Mar 1, 2002 3:21 AM by Stephen White

    standalone client: SecurityException: no protocol: auth.conf

    David M. Karr Newbie

      I'm trying to set up the file-based JAAS sample described in the docs, but with my own beans, instead of the beans in the sample, and I'm using a standalone client, instead of a servlet.

      I think I have everything set up, including putting the "client/auth.conf" into the client jar file.

      Unfortunately, when my client tries to create the LoginContext, I get the following exception:

      java.lang.SecurityException: no protocol: auth.conf
      at com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221)
      at javax.security.auth.login.LoginContext.init(LoginContext.java:172)
      at javax.security.auth.login.LoginContext.(LoginContext.java:319)

      I know that the client is reading the auth.conf file, because before I copied the "client/auth.conf" file and set the "java.security.auth.login.config" property, I was getting a different exception, "Unable to locate a login configuration".
      What could be going wrong here? Is there some way to get more information? Is there someplace where this is well-documented?

      Just in case, I'll include the "auth.conf" file here:
      other {
      // Put your login modules that work without jBoss here

      // jBoss LoginModule
      org.jboss.security.ClientLoginModule required;

      // Put your login modules that need jBoss here