Shibboleth Upgrade Guide

From b8ba26099e23b4221bbb32e3ad962fd9dd0d1cb7 Mon Sep 17 00:00:00 2001 From: wassa Date: Fri, 30 Apr 2004 16:09:09 +0000 Subject: [PATCH] Remove 1.1-related guide. git-svn-id: https://subversion.switch.ch/svn/shibboleth/java-idp/trunk@1042 ab3bd59b-922f-494d-bb5f-6f0a3c29deca --- doc/UPGRADE-GUIDE.html | 227 ------------------------------------------------ 1 file changed, 227 deletions(-) delete mode 100644 doc/UPGRADE-GUIDE.html diff --git a/doc/UPGRADE-GUIDE.html b/doc/UPGRADE-GUIDE.html deleted file mode 100644 index ee4a963..0000000 --- a/doc/UPGRADE-GUIDE.html +++ /dev/null @@ -1,227 +0,0 @@ - - - - - - Shibboleth Upgrade Guide - - - - - - -

Shibboleth Upgrade Guide

- - Shibboleth Upgrade Guide
-Shibboleth Version 1.1
-July 29, 2003
- -
-

-
- -

-Latest Origin Upgrade -

-Latest Target Upgrade -

- -

This guide contains suggested steps to upgrade from a Shibboleth 1.0 installation to a Shibboleth 1.1 installation. There are many ways to do this and some steps may need to be modified to reflect differences in the local installation.

- -

Shibboleth 1.1 is fully backward compatible with Shibboleth 1.0; however, some features have been deprecated, so all deployments are highly encouraged to move to current configurations. For a full list of new and changed functionality, consult the header of the Shibboleth Deployment Guides.

- -

Origin

- -

v1.0 to v1.1

- -

All Shibboleth 1.0 configuration specifications are still current as of Shibboleth 1.1.

- -

Shutdown Tomcat. -
Copy the following files to a scratch directory: -
1. origin.properties (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/origin.properties)
2. resolver.xml (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/resolver.xml)
3. The logging configuration file (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/log4j.properties)
4. The HS' Keystore (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/keystore.jks)
5. The web application deployment descriptor (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/web.xml)
6. Any created ARP's (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/arps/*)
7. The crypto handle repository keystore (if used) (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/handle.jks)
8. The targetedId attribute keystore (if used) (defaults to $CATALINA_HOME/webapps/shibboleth/WEB-INF/classes/conf/persistent.jks)
-
Delete the old origin.
Deploy the new origin.
Copy over the files from the scratch directory.
Start up Tomcat.

- -

Target

- -

v1.0 to v1.1

- -

Shibboleth 1.1 handles attributes differently than 1.0. Attributes are now added to the target in one place rather than three. The [attributes] section may be deleted -from shibboleth.ini, and all ShibMapAttribute commands maybe be removed from the Apache configuration. -Any customization of the ShibMapAttribute parameters needs to be reflected in AAP.xml, as documented in the Shibboleth Target Deploy Guide.

- -

Stop the SHAR and Apache.
Move the old Shibboleth to a new folder: -
- $ mv /opt/shibboleth /opt/shibboleth-old -
-
Unpack/install the new .tarball into /opt/shibboleth.
Copy the old configuration files back into the new Shibboleth's folder: -
- $ cp /opt/shibboleth-old/etc/shibboleth/shibboleth.ini \
-      /opt/shibboleth-old/etc/shibboleth/*.xml \
-      /opt/shibboleth-old/etc/shibboleth/*.log* \
-      /opt/shibboleth-old/etc/shibboleth/*.html \
-      /opt/shibboleth/etc/shibboleth -
-
If changes have been made to apache.config and -it is being used to configure Apache, it should be copied over as well in a similar fashion.
Copy over the SHAR's key and certificate if they are stored in the old /opt tree. -
Restart the target.

- - - - -- 1.7.10.4