Currently I am working at a big Enterprise where they use Tivoli Access Manager as authorization and authentication source for a lot of there applications.
This Enterprise is using JBoss as open source application server platform and is using this more and more. When they began using JBoss they got a TAM plug-in for JBoss from IBM. This plug-in did the complete authorization and authentication by implementing JAAS and registering all the used security roles in TAM. This is done during deployment time.
If you have an application with a lot of roles this is very frustrating because it can take a lot of extra time to start up (think of 30 minutes per application) because TAM is synchronizing all the new roles.
Most applications at this customer are using JAAS but do not have special method level authorizations implemented by using TAM. So only the roles are important.
After realizing this I thought is could be a good idea to create a simpler solution for integration TAM and JBoss. For this I wrote some custom code (only 250 lines).
Things to keep in mind
This method is using the iv-user and iv-groups headers at http transport level. Without transport level security (i.e. ssl) it is possible to fake this by using a man in the middle attack.
If you have proper firewall rules and security zones this does not have to be a problem.
When using this method you can use a mapping file for mapping TAM roles to application roles. With the TAM module this can be centrally managed. But since these roles normally only change at deployment time I don’t think this is a real problem.
The steps to use this solution
Download the plugin including all sources here.
Add the jboss_sso_tam.jar file to the server classpath (server/[profile]/lib)
Set the authorization method to BASIC in the web.xml inside the application (application.war/WEB-INF/web.xml).
Set the roles in the web.xml (or in annotations). See http://java.sun.com/javaee/5/docs/tutorial/doc/bncav.html for more information about security roles in Java.
Add the TAM JBoss authorization Valve to the web deployer (apache). This can be done by editing jboss.web-deployer/META-INF/jboss-service.xml inside the deploy directory inside a server profile.
This authorization Valve is called before the servlet or static content is called for each request. It is important that the key is set to the same value as the authorization method in the web.xml inside the application (see step 2).
|<attribute name=”Authenticators” serialDataType=”jbxb”>…
Edit the login-config.xml file inside the server/[profle]/conf directory. Here you have to add the login-module to the application-policy which is used. In this example case I edited the jmx-console policy. The security domain for an application defaults to the name of the war or ear file. (i.e. jmx-console.war Ý jmx-console).
You can override the security domain in a jboss-web.xml file in the WEB-INF directory of an application.
|<application-policy name = “jmx-console”><authentication>
<application-policy name = “jmx-console”>
flag = “required”>
After editing the login-config.xml file it is possible to use a mapping file for mapping the tam roles to application roles. Default you can use the server/[profile]/conf/props/tamroles.properties file for this.
The name of this file can be overridden with a module-option tag with the name tamrolesProperties.