[jboss-jira] [JBoss JIRA] (JBWEB-228) Globally configure an Authenticator Valve for the whole JBoss.

[ https://issues.jboss.org/browse/JBWEB-228?page=com.atlassian.jira.plugin.... ] karin k commented on JBWEB-228: ------------------------------- This would not solve the requirement of making the authenticator globally available (and manageable by means of DMR). Our approach is to install JBoss runtimes in a most suitable way for our customers and take the burden from them to know the insights of JBoss in details. Formerly with JBoss 4.2.3 we have enhanced JBoss Web to know our Authenticator (in some intrusive way). Afterwards enabling the Authenticator was just using it in the auth-method (which was easy and handy). Using your proposed approach would mean that the developer or application deployer has to know how configure the valve, where to get the classes from. From my point of view this sounds tricky and not easy at all. You might say that we could still enhance JBoss Web as we did before. This is correct. But our intent is to switch from the Community Version towards the EAP version. And I'm not sure if we are allowed to do such hacks in the EAP version. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira