4 Replies Latest reply on Aug 25, 2016 11:05 AM by Marc Rosenthal

    custom DatabaseServerLoginModule not working in wildfly 10+

    Marc Rosenthal Newbie

      In Wildfly 9, I had a working custom login module.  It was a class that extended org.jboss.security.auth.spi.DatabaseServerLoginModule.  I declare it in the standalone.xml with:


      <login-module code="com.at.security.auth.spi.CustomDatabaseServerLoginModule" flag="required" module="com.at.jboss-login-module">




      In Wildfly 10 and 10.1, it does not work.  I even stripped out all custom code from it so it looks like:


      public class CustomDatabaseServerLoginModule extends DatabaseServerLoginModule {




      I don't get any errors and my debug points are never hit.  It works in (in Wildfly 10 and 10.1) as soon as I switch the standalone.xml back to:


      <login-module code="Database" flag="required">


      It seems like those two cases would be the same though (a custom DatabaseServerLoginModule with no overwritten methods and  the default DatabaseServerLoginModule).  I don't see anything here Security subsystem configuration - WildFly 10 - Project Documentation Editor that indicates it changed or that I am doing anything incorrectly.  I have turned on TRACE logging for org.jboss.security and org.jboss.as.security but I don't see anything.  Does anyone know what might be happening here?