[ https://issues.jboss.org/browse/WFLY-2850?page=com.atlassian.jira.plugin.... ] Sylvain Brouillat edited comment on WFLY-2850 at 3/14/14 7:28 AM: ------------------------------------------------------------------ I wasn't using AS7/EAP6 but an old configuration AS4, and tomcatAuthentication was set to false by adding ajp connector configuration in server/default/deploy/jbossweb-tomcat55.sar/server.xml : <Connector port="8009" address="bind.address" emptySessionPath="true" enableLookup="true" redirectPort="8443" protocol="AJP/1.3" tomcatAuthentication="false" /> It exists a different way to disable tomcatAuthentication in JBoss7.1 from system-properties (https://issues.jboss.org/browse/WFLY-254). You've said : "I have implemented an authenticator based on this in Undertow", are you talking about io.undertow.security.impl.ExternalAuthenticationMechanism class ? Is there a way to enable it from wildfly standalone.xml configuration ? Like using <system-properties> or something else ? was (Author: sylvain.b): Tomcat define tomcatAuthentication attribute for ajp connector, that when set to false, disable tomcatAuthentication and allows apache to handle authentication and pass remote_user throught AJP channel to tomcat (http://tomcat.apache.org/tomcat-7.0-doc/config/ajp.html). I wasn't using AS7/EAP6 but an old configuration AS4, and tomcatAuthentication was set to false by adding ajp connector configuration in server/default/deploy/jbossweb-tomcat55.sar/server.xml : <Connector port="8009" address="${bind.address}" emptySessionPath="true" enableLookup="true" redirectPort="8443" protocol="AJP/1.3" tomcatAuthentication="false" /> It seems to exist a different way to disable tomcatAuthentication in JBoss7.0 (https://issues.jboss.org/browse/WFLY-254). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira