2 Replies Latest reply on Feb 24, 2004 12:24 PM by mike andrews

    per-app configuration

    mike andrews Newbie

      hi folks,

      what i'd like to do is avoid touching global server configuration files, and put all local/custom configuration into my application's *.ear file.

      what i've done so far successfully is write my own LoginModule class and gotten it to work in my application using jboss-3.2.3, by (1) dropping the jar in the server/all/lib directory, (2) adding an application-policy element to server/all/conf/login-config.xml, and (3) referencing that policy in the jboss-web.xml of my web app. that works fine...

      but instead of putting stuff in the server-global login-config.xml etc., can i include something like a local-login-config.xml in my *.ear? no luck so far trying. even better, can i also put my LoginModule class's jar in the *.ear too? that would be true hot-deploy, if so!

      thanks in advance,

        • 1. Re: per-app configuration
          Wonne Keysers Newbie

          You can embed a .SAR with the config below in your .EAR.
          Just put the login-config.xml in the .SAR's META-INF/.
          It works in the latest snapshot (3.2.4RC1), but I don't know if it were already in the 3.2.3 package...

          <mbean code="org.jboss.security.auth.login.DynamicLoginConfig" name="test:service=SecurityService">
           <attribute name="AuthConfig">META-INF/login-config.xml</attribute>
           <depends optional-attribute-name="LoginConfigService">jboss.security:service=XMLLoginConfig</depends>

          • 2. Re: per-app configuration
            mike andrews Newbie

            thanks so much!

            looks like its not in 3.2.3, but i'll upgrade to the cvs HEAD for jboss-3.2 to take advantage of this feature.