2 Replies Latest reply on Aug 23, 2012 11:01 AM by pugsherpa

    subject-factory no longer part of security schema?

    pugsherpa Newbie

      I was trying to resolve our Unauthenticated caller: null error  by creating a custom subject factory that won't try to authenticate the subject, just return it.  However, I just noticed that from the jboss-as-security_1_0.xsd to jboss-as-security_1_1.xsd the subject-factory element is missing.

       

      I got the impression that I could create a custom subject factory from this article:  https://docs.jboss.org/author/display/AS7/Security+subsystem+configuration

       

      Is this article out-of-date?  Is subject factory no longer supported?

       

      How can I get around the forced authentication that is done by the JbossSecuritySubjectFactory, which will always throw an exception for us because we don't expect the subject to be validated ( the way JbossSecuritySubjectFactory tries to validate) for some of our domains?  Do I have to write my own AuthenticationManager? 

        • 1. Re: subject-factory no longer part of security schema?
          pugsherpa Newbie

          Ok, I also noticed that the property

           

          authentication-manager-class-name

           

          is no longer in the jboss-as-security_1_1.xsd schema.

           

          What is going on here?!

          • 2. Re: subject-factory no longer part of security schema?
            pugsherpa Newbie

            The error:

             

             

            {code}

            TRACE [org.jboss.security.authentication.JbossCachedAuthenticationManager] Begin isValid, principal:null, cache entry: null

            TRACE [org.jboss.security.authentication.JbossCachedAuthenticationManager] defaultLogin, principal=null

            ERROR [org.jboss.security.authentication.JbossCachedAuthenticationManager] Login failure: javax.security.auth.login.LoginException: unable to find LoginModule class: fishsthore.HibernateLoginModule from [Module "org.picketbox:main" from local module loader]

            TRACE [org.jboss.security.authentication.JbossCachedAuthenticationManager] End isValid, false

            ERROR [org.jboss.as.connector.subsystems.datasources.AbstractDataSourceService$AS7DataSourceDeployer] Exception during createSubject() PB00024: Acess Denied: Unauthenticated caller: null: java.lang.SecurityException: PB00024: Access Denied: Unauthenticated caller: null

            ....

            {code}

             

            Our custom login modules are part of the ear, not deployed as their own modules.