IdP Stopped Upon Tomcat Restart

One of the most common problems why the IdP does not start is malformed configuration files. In many cases this causes the xerces library which handles the parsing of the configuration files to throw exceptions. Check that your ARPs file, idp.xml and resolver configuration file have the correct syntax and well-formed.

One approach to check if your resolver or IdP is ok by executing:

   export IDP_HOME=/usr/local/shibboleth-idp
   export SHIB_HOME=$IDP_HOME
   $SHIB_HOME/bin/resolvertest --idpXml=file://$SHIB_HOME/etc/idp.xml --user=joe --requester=urn:mace:federation.org.au:testfed:level-1:sp-dspace1.mams.org.au

If it fails, try to put --debug option to see what's going on.

You can put --file=file://$SHIB_HOME/etc/resolver.ldap.xml instead of the --idpXml

Make sure --user is an existing user.

--requester allows you to see the response specifically to a particular SP, this is useful when a particular SP doesn't work as expected.