0 Replies Latest reply on May 22, 2014 11:18 AM by Juergen H

    wildfly8 security domain configuration: ear-packaged?, complex login module properties via jaxp?

    Juergen H Newbie

      I'm currently working to migrate a - basically - web app from jboss-4.2.3.GA to wildfly8


      In jboss4 I have:

      * jaas login-service.xml packaged in MYAPP.ear with META-INF/jboss-app.xml <module><service>login-service.xml</service></module>

      it's my understanding thats not possible any more with wildfly, I have to relocate login-config to /standalone.xml ?


      btw, I have a hard time getting used to this non-modularized,non-commentable,server-written,monolithic big-junk config file.

      On the other hand, /conf/jboss-service.xml wasn't too small either


      * jaas login config included a custom RegExpXMLLoginModule, that would do regular expression based matching and rewriting for username/password/groups

      while no such module exists for wildfly out-of-the-box?, I can still create custom jaas login modules.


      * jaas login config included complex login module properties that where parsed via jaxp in jboss-4.2.3.GA (?) and allowed creating of non-string login module properties


      <jaas:login-module code="RegExpXMLLoginModule" flag="optional">
       <jaas:module-option name="userInfo">
         xsi:schemaLocation="urn:XXX:regExpUsers:1.0 resource:RegExpUsers_1_0.xsd"
         <ur:user name="(.*)" derivedUsername="{0}">
          <ur:role name="auth-by-xml" />
          <ur:role name="auth-by-xml" group="auth-info"/>


      as module-options in wildfly8 are restricted to simple strings (I don't get while jaxp xml-to-pojo capability was removed),
      I guess the best practice would be to create some configuration file an place it in classpath of application/jbossas ? similar to user.properties,roles.properties