3 Replies Latest reply on Oct 29, 2001 12:43 PM by J. Wolfgang Kaltz

    JAAS / ErrorMessage

    georg Newbie

      Argh.

      I the Error: CONTAINER EXCEPTION:Configuration Error:
      Line 102: expected 'option key', found 'null'


      The trace on the serverside shows me that there goes something wrong at: com.sun.security.auth.login.ConfigFile.getAppConfigurationEntry(ConfigFile.java:221) But this is a com.sun class and I do not have the source for that file.

      The client side is somekind of more informative and writes: Container exception. Notify the container developers :-); nested exception is: ....

      Hmmm. This is surely a configuration error, but I can't figure out where I made the mistake. If anybody could help... that would be fine.

      ps: LoginContext.login() works without throwing an Exception.

        • 1. Re: JAAS / ErrorMessage
          J. Wolfgang Kaltz Novice

          What does your entry in your auth.conf look like ? Probably you misplaced a ; or something, see the other post from today regarding this.

          • 2. Re: JAAS / ErrorMessage
            georg Newbie

            That brings up another question.

            Where do I have to place the file "auth.conf" and how do I find out which file had been used to configure jaas.

            If I understood it right there should be one file in Jboss/conf/tomcat and one file on the client side in the classpath.

            am I right?

            • 3. Re: JAAS / ErrorMessage
              J. Wolfgang Kaltz Novice

              > Where do I have to place the file "auth.conf" and how
              > do I find out which file had been used to configure
              > jaas.

              For details, check the online documentation + the JBossSX article in JavaWorld.

              My 2 Rappen :
              whenever you do a JAAS login, the default JAAS behaviour will be to look for an auth.conf (see Sun's JAAS doc to see how exactly it does this) and for an entry corresponding to the name you've given. The JBoss container will try to do such a login if you're accessing a bean which you've deployed within a security context (the name of security context is the entry in the auth.conf that will be looked up)

              > If I understood it right there should be one file in
              > Jboss/conf/tomcat and one file on the client side in
              > the classpath.

              Actually Tomcat's auth.conf is your client side configuration (Tomcat being the JBoss client), so you've got one for Tomcat, and one for JBoss: jboss/conf//auth.conf (containing, at the minimum, the security domains you're using in the deployment)