[
https://issues.jboss.org/browse/JBWEB-228?page=com.atlassian.jira.plugin....
]
Remy Maucherat commented on JBWEB-228:
--------------------------------------
Not necessarily. Valves (like filters and servlets) can be added through metadata, so a
service can add one to every webapp.
[BTW, your authenticator is a container component already, you'd have to put it in a
custom module, so if it's allowed, means to add it will be allowed]
OTOH, I don't consider using jboss-web.xml to declare that valve for every webapp to
be so bad.
Globally configure an Authenticator Valve for the whole JBoss.
--------------------------------------------------------------
Key: JBWEB-228
URL:
https://issues.jboss.org/browse/JBWEB-228
Project: JBoss Web
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: JBossWeb-7.0.0.GA, JBossWeb-7.0.1.GA , JBossWeb-7.0.2.GA,
JBossWeb-7.0.9.GA
Reporter: Mo Zo
Assignee: Remy Maucherat
Please add an option to set and configure an Authenticator (Valve) globally for all
applications in a JBoss by using standard JBoss mechanisms like domain.xml, standalone.xml
and DMR, so that it would be possible to reference an Authenticator like this:
web.xml
<login-config>
<auth-method>CUSTOM</auth-method>
</login-config>
To achieve this I had to modify:
...\modules\org\jboss\as\web\main\jbossweb-7.0.X.Final.jar\org\apache\catalina\startup\Authenticators.properties
CUSTOM=<full qualified authenticator class name>
which certainly is not a good way.
--
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