The Shibboleth V2 IdP and SP software have reached End of Life and are no longer supported. This documentation is available for historical purposes only. See the IDP v4 and SP v3 wiki spaces for current documentation on the supported versions.

IdPQuickInstallTest

Owned by Rod Widdowson
Last updated: Sept 27, 2013 by kefo1760@colorado.edu
2 min read

Testing a Quick Install IdP

Once the Installer has completed, the first stage is to progressively test the system.

  1. Testing Tomcat
    First, test the Tomcat installation by browsing to https://localhost. It is usual to get a certificate error.
    As mentioned above, access to the "Tomcat Manager" application is achieved by providing the username 'administrator' and its password in the Active Directory Domain.
    Any errors encountered at this stage will require access to the Tomcat logs, which are in the CaptiveTomcat6\logs subdirectory of the installation directory.
  2. Testing Tomcat and the IdP Installation
    Test the IdP Installation by browsing to https://localhost/idp/status. Any errors encountered at this stage will require access to the IdP logs, which are in the ShibIdP\logs subdirectory of the installation directory.
  3. Testing the IdP Installation against an SP
    The easiest way to test the installation is via TestShib. The generated metadata is suitable for insertion directly into TestShib (via the "Edit XML..." button).
    Any errors encountered at this stage will require access to the IdP logs, which are in the ShibIdP\logs subdirectory of the installation directory, and the SP logs, which are available via the TestShib test pages.
    With the IdP working, the rest of the configuration is as described elsewhere.
  4. Testing against your federation
    Prior to testing against your home federation you need to configure your IdP to with with it. This is described here
    That done you should consult your federation operator for details on how to test against their test SPs