Preparing JBoss for the Shibboleth Identity Provider
- JBoss AS 5 or greater
- Java 6 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.
Recommended Configuration Changes
- Limit the allowed size of POST submissions to any HTTP or AJP connectors (including the SOAP connector below) by adding the
maxPostSizeattribute. A size of 200K (204800) is a reasonable choice.
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).
- Download tomcat6-dta-ssl-1.0.0.jar (asc) in to server/<serviceProfile>/deploy/jboss-web.sar/
Add the following Connector definition into JBoss Tomcat's server/<serviceProfile>/deploy/jboss-web.sar//server.xml.
IDP_HOMEwith the IdP home directory entered during installation.
PASSWORDwith the password for the IdP key entered during installation.