...
| Panel |
|---|
The most current installers from Internet2 can always be found at http://shibboleth.internet2.edu/downloads.html The link provided above should be used if you are installing a 2.x Service Provider (SP). Historical installers: Please note that we strongly recommend that no new systems be created using Shibboleth 1.3x. This software will reach its end of life on June 30th, 2010. At that time, security updates for the software will no longer be created. If you still have some need to obtain the 1.3x packages, for now they can still be obtained from Internet 2. 1.3x RPMs remain available from Internet2 for RHEL 4 and 5. You will typically need the 5 main RPMs: log4shib, opensaml, shibboleth, xerces-c, xml-security-c. A 1.3x installer for IIS is also available from Internet2. Some other Linux distributions also maintain binary installers available from the OS distribution point. If you have questions about other distributions please contact touchstone-support and indicate what operating distribution and version you are using. |
...
| Panel |
|---|
The Touchstone team recommends that you use the installers available from Internet2 or your operating system vendor. However, if you need to build from source, the Touchstone team maintains a source tarball of tbe Shibboleth SP, including all of its immediate prerequisites (curl, log4shib, xerces-c, xml-security-c, and opensaml), and a script to perform the entire build, in the touchstone locker, in /mit/touchstone/shibboleth/source/shibboleth-sp-sources.tgz. The script can build the software on Linux and Solaris systems; note that you will to need to have Apache httpd (preferably 2.x, though 1.3 should also work) and OpenSSL (0.9.7 or higher) installed on the system, including their development packages. On Solaris systems, you must have the native Sun C/C++ compiler installed; Athena Solaris machines have this available, via attachandrun scripts and the sunsoft locker, but this requires that you have AFS tokens for the athena cell. Solaris machines must also have GNU make (gmake) installed. To build from this, create a build directory, and unpack the source tarball into it; use the build-sp.sh script as follows: # sh build/build-sp.sh -a <apxs_path> -p <install_prefix> -s openssl_prefix please read the following pages:
Once you have built the software successfully, you will need to configure and customize it for use. |
...
| Panel |
|---|
Note: Before proceeding to "Configuration and customization for use" you should obtain a server certificate. Please make sure that you use lower case servernames in your certificate request. The server name within the certifiacte is case sensitive. Information about how to generate a certificate request and where to send the request can be found in https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/display/WSWG/How+to+acquire+and+verify+a+M.I.T.+x509+Server+Certificate Historical note: If your server already has a server certificate issued by the MIT Certificate Authority, and it was issued after July 1st, 2008, and it has not expired, you should be able to use it with Shibboleth/MIT Touchstone. If the server certificate was issued prior to July 1st, 2008, you probably need to obtain a new server certificate.Please make sure that you use lower case servernames in your certificate request. The server name within the certifiacte is case sensitive.Information about how to generate a certificate request and where to send the request can be found in https://wikis.mit.edu/confluence/display/WSWG/server+certificates Only section one of the above document is directly applicable to your configuration at this time. |
*Configuration and customization for use *
| Panel |
|---|
Note: The gen-shib.sh procedure described below currently works only on Linux and Solaris systems; it should be portable to other UNIX-based systems without too much effort. When you have successfully built and installed the Shibboleth SP, you will need to configure things to work against our test and pilot IdPs. We have some template files and a script in AFS (the touchstone locker) to generate the needed config files from the templates: cd to shibboleth's etc directory ($prefix/etc/shibboleth), and copy in the following files from /mit/touchstone/shibboleth/config/shibboleth-sp/ (or just copy all files from the directory):
Note: If you do not have AFS installed on your server, then you can access the above files via http, either from a browser or using wget. The URL is http://web.mit.edu.ezproxyberklee.flo.org/touchstone/shibboleth/config/shibboleth-sp/ On Solaris, also copy:
Then run the gen-shib.sh script: sh ./gen-shib.sh and answer its prompts, which will hopefully be clear. Remember that the certificate it wants should be enabled for client as well as server use. Any MIT server certificates that have been created after July of 2008 will be enabled for client as well as server use. The $prefix/etc/shibboleth directory will contain apache.config, apache2.config, and apache22.config, which contain needed and example directives for Apache 1.3, Apache 2.0, and Apache 2.2, respectively; copy and/or include the appropriate file in your Apache config, and customize as needed. The directory also contains a shibd init script for Red Hat (shibd-redhat) and Debian (shibd-debian) systems. On Red Hat machines, copy shibd-redhat to /etc/init.d/shibd, make sure it is executable, add it as a managed service with "chkconfig --add shibd", and enable it for run levels 3, 4, and 5 ("chkconfig --level 345 shibd on"). On Solaris machines, the gen-shib.sh script will generate a shibd init script (from shibd.in); this should be installed into /etc/init.d, and configured to start at boot time, after httpd has started. NOTE: shibd is a daemon that must be running, so make sure it is started at boot time, after Apache httpd has been started. The Shibboleth Apache module logs by default to $prefix/var/log/httpd/native.log. This file must be writable by Apache, which may require that you set its directory's ownership and/or permissions to allow write access by the user Apache is configured to run under. You may also choose to change the location of the file, by modifying the log4j.appender.native_log.fileName setting in $prefix/etc/shibboleth/native.logger. For information on configuring Shibboleth to protect content, see the Shibboleth wiki at Internet2, as well as the information in the sections below. You will probably also want to customize the error pages and support contact information listed in the Errors element in $prefix/etc/shibboleth/shibboleth.xml (search for "You should customize these pages!"), e.g.: <Errors session="/usr/local/shibboleth/etc/shibboleth/sessionError.html" metadata="/usr/local/shibboleth/etc/shibboleth/metadataError.html" rm="/usr/local/shibboleth/etc/shibboleth/rmError.html" access="/usr/local/shibboleth/etc/shibboleth/accessError.html" ssl="/usr/local/shibboleth/etc/shibboleth/sslError.html" supportContact="root@localhost" logoLocation="/shibboleth-sp/logo.jpg" styleSheet="/shibboleth-sp/main.css"/> The pages are used as follows:
|
...
Keep your metadata up to date
| Panel | ||
|---|---|---|
|
Example code and configuration information for third party applications
...
| Panel | |||||
|---|---|---|---|---|---|
|
