The EDS is made available as a noarch RPM. This allows you to manage your installation and perform upgrades in an automated fashion. Given that the EDS is entirely in "webspace", you can certainly choose to deploy it yourself (see the section on Other Platforms).

Installing via Yum

The RPM repositories for each platform we support are available by accessing the web form at https://shibboleth.net/downloads/service-provider/RPMS/ to generate the appropriate file to place in your repository directory (typically /etc/yum.repos.d/).

You can turn the repository on and off by adjusting the "enabled" property in the file, such as to prevent automated updates and maintain manual control. While enabled, the yum command will "see" the Shibboleth packages when you perform standard operations, and installing the EDS should require only a single command:

$ yum install shibboleth-embedded-ds

Installing Manually

If you prefer to install by hand, you can find the source distribution at https://shibboleth.net/downloads/embedded-discovery-service/

Installation details.

The Installation places the files you will need to configure the EDS into /etc/shibboleth-ds.

It then configures the Apache webserver to serve the EDS files (including the ones you use to configure) as:

/shibboleth-ds/idpselect_config.js
/shibboleth-ds/idpselect.js
/shibboleth-ds/idpselect.css
/shibboleth-ds/index.html used for testing

The Embedded Discovery Service (EDS) is a set of CSS and Javascript files. To install them you'll need to serve these files up via your web server. Refer to your web server documentation if you're unsure how to serve up static documents.

Web Server Setup

1. Download the Embedded Discovery Service Distribution

2. Unzip the distribution

3. Copy the Javascript files (idpselect_config.js and idpselect.js, and the CSS (idpselect.css) files in to the location from where your web server is serving static content.

4. For testing purposes you may chose to copy the index.html file to the same location.

Once complete, open a browser and test to make sure each file is reachable.

There are two ways to go about setting up the web page that will act as the actual discovery service.

The first way, useful for testing, is to use the index.html file that comes with the EDS distribution.

If, however, you'd like to embed the discovery service in to an existing page template you have for your site (the behavior we'd expect for an production install) then make the following modifications to your HTML page:

1. Within the head element add a link to the discovery service CSS page similar to:

   <link rel="stylesheet" type="text/css" href="idpselect.css">

2. Within the body element add the following div element in the location you wish to use for the upper-left corner of the discovery service (i.e., where you want it to start rendering):

   <div id="idpSelect"></div>

3. At the bottom of the body element (just before the closing tag) add the following script definitions:

   <!-- Load languages scripts -->
   <script src="idpselect_config.js" type="text/javascript" language="javascript"></script>
   <script src="idpselect.js" type="text/javascript" language="javascript"></script>
   

Now, if you're testing against a brand new Service Provider 2.4 install you can test at this point (since 2.4 comes with the discovery data feed configured by default). If you upgraded to 2.4 from a previous version you will need to complete the Service Provider configuration steps given in the next section before you can test.

So, if you want to and can test at this point, then open a web browser and go to the embedded discovery service page. If everything is working okay you'll see the discovery service rendered.