Preparing JBoss for the Shibboleth Identity Provider
- JBoss AS 4 or greater
- Java 5 or greater
Required Configuration Changes
- Edit your the login-config.xml configuration file and comment out the
<application-policy name = "other">element. This default policy requires that a user authentication source also report a set of roles for the user. Most deployer's will not do this during the authentication step (though they may later on during the attribute resolution step). Therefore, this policy needs to be removed.
Setting your Hostname
If your machine has more than one hostname Tomcat can become confused about which hostname it should use. In this case you should explicitly set the hostname.
- Within_server/<serviceProfile>/deploy/jboss-web.deployer/server.xml_ replace occurrences of
localhostwith the appropriate hostname for your server.
Supporting SOAP Endpoints
Shibboleth IdPs and SP may communicate directly, as opposed to sending messages via the user's browser, during certain operations (Attribute Query, Artifact Resolution, and Logout). In order to support these request the IdP needs an additional port (called a Connector within the Tomcat configuration), distinct from the one used by the user (because they have different, mutually exclusive, security requirements).
- Copy the following Connector definition into JBoss Tomcat's server/<serviceProfile>/deploy/jboss-web.deployer/server.xml. This definition should be placed either before the first, or after the last, connector already defined in the configuration file.
- Replace IDP_HOME with the directory you will install the IdP into and PASSWORD with the password you entered during installation.