...
- Prepare your Servlet container. Linux deployers may want to take a look at IdPLinuxNonRoot, which documents one way of using privileged ports. Some containers, such as Jetty, include alternatives. The links below are to (imperfect) examples provided by the project or by deployers. The list below is not reflective of the specific containers and versions we support, which is explicitly and only available on the SystemRequirements page.
- Download the latest Identity Provider software package (the zip file has Windows line endings, the tarball Unix line endings).
- Unpack the archive you downloaded to a convenient location. It will not be needed after installation.
- Change into the newly created distribution directory, shibboleth-identityprovider-VERSION
- Run either ./bin/install.sh (on non-Windows systems) or .\bin\install.bat (on Windows systems).
- The installation directory you provide will be referred to as
idp.homethroughout this documentation.
- The installation directory you provide will be referred to as
- Deploy the IdP WAR file, located in idp.home/war/idp.war. See the Servlet container preparation notes for examples on how to do this.
Controlling generated key size 3.4
In Version 3.4 the default key size has been increased. Under certain circumstances this may fail because of restrictions imposed by version of java or the java "jusrisdiction policy".
In nearly all situations this should be fixed by installing the unlimited strength Unlimited Strength Jurisdiction Policy or by updating to a more recent version of java.
If this is impossible (or if you want a different key size) you cna specify the idp.keysize parameter on the command line
| Code Block | ||||
|---|---|---|---|---|
| ||||
ant -Didp.keysize=2048 |
A Quick Test
You can test that the IdP is properly installed and is at least running successfully in the container with the status command line utility (idp.home/bin/status.sh or idp.home\bin\status.bat).
...