Shibboleth IdP v3.3.2 on Ubuntu Linux LTS 18.04

If you are looking at this guide to install your production servers/ IDPs, please consult

The following guide is intended for the workshop use only.

Installation assumes you have already installed Ubuntu Server 18.04 with default configuration and has a public IP connectivity with DNS setup

Lets Assume your server hostname as

All commands are to be run as root and you may use sudo su to become root

  1. Install the packages required:
    apt-get install vim default-jdk ca-certificates openssl tomcat8 apache2 ntp expat

  1. Modify /etc/hosts and add:
    vim /etc/hosts

(Replace with your IdP FQDN) Remember not to remove the entry for localhost.

  1. Define the costants JAVA_HOME and IDP_SRC inside /etc/environment:
  • update-alternatives --config java
    (copy the path without /bin/java)
  • vim /etc/environment
  • source /etc/environment
  • export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64
  • export IDP_SRC=/usr/local/src/shibboleth-identity-provider-3.3.2
  1. Configure Tomcat8 Defaults:
  • update-alternatives --config java
    (copy the path without /bin/java)
  • update-alternatives --config javac
  • vim /etc/default/tomcat8
    JAVA_OPTS="-Djava.awt.headless=true -XX:+DisableExplicitGC -XX:+UseParallelOldGC -Xms256m -Xmx1g"

(This settings configure the memory of the JVM that will host the IdP Web Application. The Memory value depends on the phisical memory installed on the machine. On production environment Set the "Xmx" (max heap space available to the JVM) at least to 2GB)

  1. Download the Shibboleth Identity Provider v3.3.2:
  • cd /usr/local/src
  • wget
  • tar -xzvf shibboleth-identity-provider-3.3.2.tar.gz
  • cd shibboleth-identity-provider-3.3.2
  1. Generate Passwords for later use in the installation, You will need two password strings, ###PASSWORD-FOR-BACKCHANNEL### and ###PASSWORD-FOR-COOKIE-ENCRYPTION###
  •    tr -c -d '0123456789abcdefghijklmnopqrstuvwxyz' </dev/urandom | dd bs=32 count=1 2>/dev/null;echo

  1. Run the installer to install Shibboleth Identity Provider v3.3.2:
  •    ./bin/
       root@idp:/usr/local/src/shibboleth-identity-provider-3.3.2# ./bin/
       Source (Distribution) Directory(press <enter> to accept default): [/usr/local/src/shibboleth-identity-provider-3.3.2]
       Installation Directory: [/opt/shibboleth-idp]
       Hostname: [localhost.localdomain]
       SAML EntityID: []
       Attribute Scope: [localdomain]
       Backchannel PKCS12 Password: ###PASSWORD-FOR-BACKCHANNEL###
       Re-enter password:           ###PASSWORD-FOR-BACKCHANNEL###
       Cookie Encryption Key Password: ###PASSWORD-FOR-COOKIE-ENCRYPTION###
       Re-enter password:              ###PASSWORD-FOR-COOKIE-ENCRYPTION###

Replace with your Domain Name

From this point there will be a variable idp.home pointing to the directory: /opt/shibboleth-idp

  1. Import the JST libraries to visualize the IdP status page:
  •    cd /opt/shibboleth-idp/edit-webapp/WEB-INF/lib
  •    wget
  •    cd /opt/shibboleth-idp/bin ; ./
  1. Change the owner to enable tomcat8 user to access on the following directories:
  •    chown -R tomcat8 /opt/shibboleth-idp/logs/
  •    chown -R tomcat8 /opt/shibboleth-idp/metadata/
  •    chown -R tomcat8 /opt/shibboleth-idp/credentials/
  •    chown -R tomcat8 /opt/shibboleth-idp/conf/
  1. Create a Certificate and a Key self-signed for HTTPS and enable secure apache web server as the front-end. (Skip step 10 if you are installing IDP on a production environment)
  •    mkdir /root/certificates
  •    openssl req -x509 -newkey rsa:4096 -keyout /root/certificates/idp-key-server.key -out /root/certificates/idp-cert-server.crt -nodes -days 1095


  •    chmod 400 /root/certificates/idp-key-server.key
  •    chmod 644 /root/certificates/idp-cert-server.crt

Create the file /etc/apache2/sites-available/idp-ssl.conf as follows:

   <IfModule mod_ssl.c>
      SSLStaplingCache        shmcb:/var/run/ocsp(128000)
      <VirtualHost _default_:443>
        DocumentRoot /var/www/html
        SSLEngine On
        SSLProtocol All -SSLv2 -SSLv3 -TLSv1 -TLSv1.1

        SSLHonorCipherOrder on

        # Disable SSL Compression
        SSLCompression Off
        # OCSP Stapling, only in httpd/apache >= 2.3.3
        SSLUseStapling          on
        SSLStaplingResponderTimeout 5
        SSLStaplingReturnResponderErrors off
        # Enable HTTP Strict Transport Security with a 2 year duration
        Header always set Strict-Transport-Security "max-age=63072000;includeSubDomains;preload"
        SSLCertificateFile /root/certificates/idp-cert-server.crt
        SSLCertificateKeyFile /root/certificates/idp-key-server.key
        #SSLCertificateChainFile /root/certificates/publicCA.crt

Enable proxy_http, SSL and headers Apache2 modules:

  •    a2enmod proxy_http ssl headers alias include negotiation
  •    a2ensite idp-ssl.conf

Configure Apache2 to redirect all on HTTPS:

  •    vim /etc/apache2/sites-enabled/000-default.conf

   <VirtualHost *:80>
        ServerName ""
        Redirect "/" ""
  •    service apache2 restart

Configure SSL on Apache2 with Letsencrypt (for Production Servers)

For tutorial purposes, implementing https was done with self-signed certificates. Therefore, please skip to step 14.

  1. Disable default apache configuration:
  •    a2dissite 000-default

  1. Create a new configuration file as idp.conf with the following:
  •    vim /etc/apache2/site-available/idp.conf
       <VirtualHost *:80>
         DocumentRoot /var/www/html

Enable Apache2 modules:

  •    a2enmod proxy_http ssl headers alias include negotiation

Restart the Apache service:

  •    service apache2 restart
  1. Install Letsencrypt and enable HTTPS:
  •    add-apt-repository ppa:certbot/certbot
  •    apt install python-certbot-apache
  •    certbot --apache -d

   Plugins selected: Authenticator apache, Installer apache
   Enter email address (used for urgent renewal and security notices) (Enter 'c' to

   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Please read the Terms of Service at You must
   agree in order to register with the ACME server at
   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   (A)gree/(C)ancel: A

   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Would you be willing to share your email address with the Electronic Frontier
   Foundation, a founding partner of the Let's Encrypt project and the non-profit
   organization that develops Certbot? We'd like to send you email about our work
   encrypting the web, EFF news, campaigns, and ways to support digital freedom.
   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   (Y)es/(N)o: Y
   Obtaining a new certificate
   Performing the following challenges:
   http-01 challenge for
   Waiting for verification...
   Cleaning up challenges
   Created an SSL vhost at /etc/apache2/sites-available/idp-le-ssl.conf
   Enabled Apache socache_shmcb module
   Enabled Apache ssl module
   Deploying Certificate to VirtualHost /etc/apache2/sites-available/idp-le-ssl.conf
   Enabling available site: /etc/apache2/sites-available/idp-le-ssl.conf
   Please choose whether or not to redirect HTTP traffic to HTTPS, removing HTTP access.
   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   1: No redirect - Make no further changes to the webserver configuration.
   2: Redirect - Make all requests redirect to secure HTTPS access. Choose this for
   new sites, or if you're confident your site works on HTTPS. You can undo this
   change by editing your web server's configuration.
   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
   Redirecting vhost in /etc/apache2/sites-enabled/rr3.conf to ssl vhost in /etc/apache2/sites-available/rr3-le-ssl.conf
   - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
   Congratulations! You have successfully enabled

Configure Tomcat 8 to run as the Back-end

  1. Modify server.xml:
  •    vim /etc/tomcat8/server.xml

Comment out the Connector 8080 (HTTP):

     <!-- A "Connector" represents an endpoint by which requests are received
          and responses are returned. Documentation at :
          Java HTTP Connector: /docs/config/http.html (blocking & non-blocking)
          Java AJP  Connector: /docs/config/ajp.html
          APR (HTTP/AJP) Connector: /docs/apr.html
          Define a non-SSL/TLS HTTP/1.1 Connector on port 8080
     <Connector port="8080" protocol="HTTP/1.1"
                redirectPort="8443" />

Enable the Connector 8009 (AJP):

     <!-- Define an AJP 1.3 Connector on port 8009 -->
     <Connector port="8009" protocol="AJP/1.3" redirectPort="443" address="" enableLookups="false" tomcatAuthentication="false"/>

Check the integrity of XML files just edited with:

xmlwf -e UTF-8 /etc/tomcat8/server.xml

If the file is well-formed, xmlwf will be silent.

  1. Create and change the file idp.xml:
  •    sudo vim /etc/tomcat8/Catalina/localhost/idp.xml
    <Context docBase="/opt/shibboleth-idp/war/idp.war"
  1. Create the Apache2 configuration file for IdP:
  •    vim /etc/apache2/sites-available/idp-proxy.conf
         <IfModule mod_proxy.c>
           ProxyPreserveHost On
           RequestHeader set X-Forwarded-Proto "https"
           <Proxy ajp://localhost:8009>
             Require all granted
           ProxyPass /idp ajp://localhost:8009/idp retry=5
           ProxyPassReverse /idp ajp://localhost:8009/idp retry=5
  1. Enable proxy_ajp apache2 module and the new IdP site:
  •    a2enmod proxy_ajp
  •    a2ensite idp-proxy.conf
  •    service apache2 restart
  1. Modify context.xml to prevent error of lack of persistence of the session objects created by the IdP :
  •    vim /etc/tomcat8/context.xml

and remove the comment from: <Manager pathname="" />

  1. Restart Tomcat8:
  •    service tomcat8 restart
  1. Verify if the IdP works by opening this page on your browser:

(you should see the IdP metadata)

If you see errors please consult log files of Tomcat8, Shibboleth or Apache. Locations are given at the end of this document

Speed up Tomcat 8 startup

  1. Find out the JARs that can be skipped from the scanning:
  •    cd /opt/shibboleth-idp/
  •    ls webapp/WEB-INF/lib | awk '{print $1",\\"}'

Insert the output list into /etc/tomcat8/ at the tail of the variable tomcat.util.scan.StandardJarScanFilter.jarsToSkip . Make sure to include the ,\ symbols at the end of the existing value when inserting.

Restart Tomcat 8:

  •    service tomcat8 restart

Configure Shibboleth Identity Provider v3.2.1 to release the persistent-id (Stored mode)

  1. Test IdP by opening a terminal and running these commands:
  •    cd /opt/shibboleth-idp/bin
  •    ./

(You should see some informations about the IdP installed)

  1. Install MySQL Connector Java and other useful libraries used by Tomcat for MySQL DB (if you don't have them already):
  •    apt-get install mysql-server libmysql-java libcommons-dbcp-java libcommons-pool-java
  •    cd /usr/share/tomcat8/lib/
  •    ln -s ../../java/mysql.jar mysql-connector-java.jar
  •    ln -s ../../java/commons-pool.jar commons-pool.jar
  •    ln -s ../../java/commons-dbcp.jar commons-dbcp.jar
  •    ln -s ../../java/tomcat-jbcp.jar tomcat-jbcp.jar

Ignore if you get errors for some of the ln commands as the files might be already there.

  1. Rebuild the idp.war of Shibboleth with the new libraries:
  •    cd /opt/shibboleth-idp/ ; ./bin/

You may need to press enter on Installation Directory: [/opt/shibboleth-idp]

  1. Create and prepare the "shibboleth" MySQL DB to host the values of the several persistent-id and StorageRecords MySQL DB to host other useful information about user consent:
  • mysql_secure_installation

This will add additional security to your database engine. For the tutorial purposes we will use Iam@2018 as passwords. Remember the capital I.

Securing the MySQL server deployment.

Connecting to MySQL using a blank password.

VALIDATE PASSWORD PLUGIN can be used to test passwords
and improve security. It checks the strength of password
and allows the users to set only those passwords which are
secure enough. Would you like to setup VALIDATE PASSWORD plugin?

Press y|Y for Yes, any other key for No: y

There are three levels of password validation policy:

LOW    Length >= 8
MEDIUM Length >= 8, numeric, mixed case, and special characters
STRONG Length >= 8, numeric, mixed case, special characters and dictionary file

Please enter 0 = LOW, 1 = MEDIUM and 2 = STRONG: 1
Please set the password for root here.

New password:Iam@2018

Re-enter new password:Iam@2018

Estimated strength of the password: 50
Do you wish to continue with the password provided?(Press y|Y for Yes, any other key for No) : y
By default, a MySQL installation has an anonymous user,
allowing anyone to log into MySQL without having to have
a user account created for them. This is intended only for
testing, and to make the installation go a bit smoother.
You should remove them before moving into a production

Remove anonymous users? (Press y|Y for Yes, any other key for No) : y

Normally, root should only be allowed to connect from
'localhost'. This ensures that someone cannot guess at
the root password from the network.

Disallow root login remotely? (Press y|Y for Yes, any other key for No) : y

By default, MySQL comes with a database named 'test' that
anyone can access. This is also intended only for testing,
and should be removed before moving into a production

Remove test database and access to it? (Press y|Y for Yes, any other key for No) : y
 - Dropping test database...

 - Removing privileges on test database...

Reloading the privilege tables will ensure that all changes
made so far will take effect immediately.

Reload privilege tables now? (Press y|Y for Yes, any other key for No) : y

All done!
  • log in to your MySQL Server with mysql -u root -p and continue.For your production servers, Make sure to replace passwords Iam@2018. When creating passwords you should consider your password policy selected above.
        SET NAMES 'utf8';
        SET CHARACTER SET utf8;
        GRANT ALL PRIVILEGES ON shibboleth.* TO root@localhost IDENTIFIED BY 'Iam@2018';
        GRANT ALL PRIVILEGES ON shibboleth.* TO shibbo@localhost IDENTIFIED BY 'Iam@2018';
        USE shibboleth;
        localEntity VARCHAR(255) NOT NULL,
        peerEntity VARCHAR(255) NOT NULL,
        persistentId VARCHAR(50) NOT NULL,
        principalName VARCHAR(50) NOT NULL,
        localId VARCHAR(50) NOT NULL,
        peerProvidedId VARCHAR(50) NULL,
        deactivationDate TIMESTAMP NULL default NULL,
        PRIMARY KEY (localEntity, peerEntity, persistentId)
        CREATE TABLE IF NOT EXISTS StorageRecords
        context VARCHAR(255) NOT NULL,
        id VARCHAR(255) NOT NULL,
        expires BIGINT(20) DEFAULT NULL,
        value LONGTEXT NOT NULL,
        version BIGINT(20) NOT NULL,
        PRIMARY KEY (context, id)
  • Restart mysql service: service mysql restart
  1. Enable the generation of the persistent-id :
  • First you need to generate a password salt. Keep a copy of the output of following as your idp.persistentId.salt
       openssl rand -base64 36
  • Edit the following file and modify the lines containing below variables.
       vim /opt/shibboleth-idp/conf/

(the sourceAttribute used in the configuration MUST BE an ldap attribute, or a list of comma-separated attributes, that uniquely identify the subject of the generated persistent-id. It MUST BE: Stable, Permanent and Not-reassignable)

     idp.persistentId.sourceAttribute = uid
     idp.persistentId.salt = Replace_these_with_your_salt_generated_earlier
     idp.persistentId.generator = shibboleth.StoredPersistentIdGenerator
     idp.persistentId.dataSource = MyDataSource
     idp.persistentId.computed = shibboleth.ComputedPersistentIdGenerator
  • Enable the SAML2PersistentGenerator:
  •    vim /opt/shibboleth-idp/conf/saml-nameid.xml

Remove the comment from the line containing:

     <ref bean="shibboleth.SAML2PersistentGenerator" />
  •    vim /opt/shibboleth-idp/conf/c14n/subject-c14n.xml

Remove the comment to the bean called "c14n/SAML2Persistent".

     <ref bean="c14n/SAML2Persistent" />
  1. Enable JPAStorageService for the StorageService of the user consent:
  • vim /opt/shibboleth-idp/conf/global.xml and add this piece of code to the tail before the ending </beans>:
     <!-- A DataSource bean suitable for use in the idp.persistentId.dataSource property. -->
     <bean id="MyDataSource" class="org.apache.commons.dbcp.BasicDataSource"
           p:validationQuery="select 1"
           p:validationQueryTimeout="5" />

     <bean id="shibboleth.JPAStorageService" class=""

     <bean id="shibboleth.JPAStorageService.entityManagerFactory"
           <property name="packagesToScan" value=""/>
           <property name="dataSource" ref="MyDataSource"/>
           <property name="jpaVendorAdapter" ref="shibboleth.JPAStorageService.JPAVendorAdapter"/>
           <property name="jpaDialect">
             <bean class="org.springframework.orm.jpa.vendor.HibernateJpaDialect" />

     <bean id="shibboleth.JPAStorageService.JPAVendorAdapter" class="org.springframework.orm.jpa.vendor.HibernateJpaVendorAdapter">
           <property name="database" value="MYSQL" />

You may need to change the password for your "shibboleth" DB in production servers)

  • Modify the IdP configuration file:
    •    vim /opt/shibboleth-idp/conf/
             idp.session.StorageService = shibboleth.JPAStorageService
             idp.consent.StorageService = shibboleth.JPAStorageService
             idp.replayCache.StorageService = shibboleth.JPAStorageService
             idp.artifact.StorageService = shibboleth.JPAStorageService
             # Track information about SPs logged into
             idp.session.trackSPSessions = true
             # Support lookup by SP for SAML logout
             idp.session.secondaryServiceIndex = true

(This will indicate to IdP to store the data collected by User Consent into the "StorageRecords" table)

  1. Connect the openLDAP to the IdP to allow the authentication of the users:
  • use openssl x509 -outform der -in /etc/ssl/certs/ldap_server.pem -out /opt/shibboleth-idp/credentials/ldap-server.crt to load the ldap certificate.

If you host ldap in a seperate machine, copy the ldap_server.crt to /opt/shibboleth-idp/credentials

  •    vim /opt/shibboleth-idp/conf/
  • Solution 1: LDAP + STARTTLS: (We recommend continuing with this option)
       idp.authn.LDAP.authenticator = bindSearchAuthenticator
       idp.authn.LDAP.ldapURL = ldap://
       idp.authn.LDAP.useStartTLS = true
       idp.authn.LDAP.useSSL = false
       idp.authn.LDAP.sslConfig = certificateTrust
       idp.authn.LDAP.trustCertificates = %{idp.home}/credentials/ldap-server.crt
       #idp.authn.LDAP.trustStore  = %{idp.home}/credentials/ldap-server.truststore
       idp.authn.LDAP.returnAttributes   = *
       idp.authn.LDAP.baseDN = ou=people,dc=instXY,dc=ac,dc=lk
       idp.authn.LDAP.userFilter = (uid={user})
       idp.authn.LDAP.bindDN = cn=admin,dc=instXY,dc=ac,dc=lk
       idp.authn.LDAP.bindDNCredential = ###LDAP_ADMIN_PASSWORD###
       idp.authn.LDAP.dnFormat = uid=%s,ou=people,dc=instXY,dc=ac,dc=lk
       idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}
       idp.attribute.resolver.LDAP.returnAttributes    = %{idp.authn.LDAP.returnAttributes}
  • Solution 2: plain LDAP

       idp.authn.LDAP.authenticator = bindSearchAuthenticator
       idp.authn.LDAP.ldapURL = ldap://
       idp.authn.LDAP.useStartTLS = false
       idp.authn.LDAP.useSSL = false
       idp.authn.LDAP.returnAttributes   = *
       idp.authn.LDAP.baseDN = ou=people,dc=instXY,dc=ac,dc=lk
       idp.authn.LDAP.userFilter = (uid={user})
       idp.authn.LDAP.bindDN = cn=admin,dc=instXY,dc=ac,dc=lk
       idp.authn.LDAP.bindDNCredential = ###LDAP_ADMIN_PASSWORD###
       idp.authn.LDAP.dnFormat = uid=%s,ou=people,dc=instXY,dc=ac,dc=lk
       idp.attribute.resolver.LDAP.returnAttributes    = %{idp.authn.LDAP.returnAttributes}

(If you decide to use the Solution 2, you have to remove (or comment out) the following code from your Attribute Resolver file:

       <dc:StartTLSTrustCredential id="LDAPtoIdPCredential" xsi:type="sec:X509ResourceBacked">
  • utility to ldap searching: ldapsearch -H ldap:// -x -b "dc=instXY,dc=ac,dc=lk" -LLL dn
  • the baseDN ==> ou=people, dc=instXY,dc=ac,dc=lk (branch containing the registered users)
  • the bindDN ==> cn=admin,dc=instXY,dc=ac,dc=lk (distinguished name for the user that can made queries on the LDAP)
  1. Enrich IDP logs with the authentication error occurred on LDAP:
  •    vim /opt/shibboleth-idp/conf/logback.xml
         <!-- Logs LDAP related messages -->
         <logger name="org.ldaptive" level="${idp.loglevel.ldap:-WARN}"/>
         <!-- Logs on LDAP user authentication -->
         <logger name="org.ldaptive.auth.Authenticator" level="INFO" />
  1. Build the attribute-resolver.xml to define which attributes your IdP can manage. Here you can find the attribute-resolver-v1-LEARN.xml provided by LEARN:
  • Download the attribute resolver provided by LEARN:
    wget -O /opt/shibboleth-idp/conf/attribute-resolver-LEARN.xml
  • Modify services.xml file: vim /opt/shibboleth-idp/conf/services.xml

must become:

  • Restart Tomcat8: service tomcat8 restart
  1. Enable the SAML2 support by changing the idp-metadata.xml and disabling the SAML v1.x deprecated support:
  •    vim /opt/shibboleth-idp/metadata/idp-metadata.xml
          <IDPSSODescriptor> SECTION:
            – From the list of "protocolSupportEnumeration" remove:
              - urn:oasis:names:tc:SAML:1.1:protocol
              - urn:mace:shibboleth:1.0
            - On <Extensions> include
                    <mdui:DisplayName xml:lang="en">Institute XY</mdui:DisplayName>
                    <mdui:Description xml:lang="en">Enter a description of your IdP</mdui:Description>
                    <mdui:Logo height="60" width="80"></mdui:Logo>
                    <mdui:Logo height="16" width="16"></mdui:Logo>
            - Upload example png files to /var/www/html as logo.png with 80x60 pixel and logo16.png with 16x16 pixel images.
            – Remove the endpoint:
              <ArtifactResolutionService Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding" Location="" index="1"/>
              (and modify the index value of the next one to “1”)
            - Remove the endpoint: 
              <SingleSignOnService Binding="urn:mace:shibboleth:1.0:profiles:AuthnRequest" Location=""/>     
            - Remove all ":8443" from the existing URL (such port is not used anymore)
            - Uncomment SingleLogoutService:
              <SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location=""/>
              <SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location=""/>
              <SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST-SimpleSign" Location=""/>
              <SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP" Location=""/>
          <AttributeAuthorityDescriptor> Section:
            – From the list "protocolSupportEnumeration" replace the value of:
              - urn:oasis:names:tc:SAML:1.1:protocol
              - urn:oasis:names:tc:SAML:2.0:protocol
            - Remove the comment from:
              <AttributeService Binding="urn:oasis:names:tc:SAML:2.0:bindings:SOAP" Location=""/>
            - Remove the endpoint: 
              <AttributeService Binding="urn:oasis:names:tc:SAML:1.0:bindings:SOAP-binding" Location=""/>
            - Remove all ":8443" from the existing URL (such port is not used anymore)
     Finally remove all existing commented content from the whole document
  1. Obtain your IdP metadata here:

If you come across an issue, check Appendix section at the end of the document to do the troubleshooting.

  1. Register you IdP on the test Federation:

    For production enviornments please use, Also make sure to remove -training from all urls.

  • When Applying for the membership of the federation the form will ask lot of questions to identify your service. Therefore, answer all of them as per the following,
  • On the IDP registration page start with pasting the whole xml metadata from and click next. If you are using a browser to open the metadata link, use its view-source mode to copy the content.
  • If you have correctly entered metadata you will be asked to select a Federation.
  • Select "Federation for Testing"
  • Fill in your contact Details
  • Go to Organization tab and Fill in all details for language English(en) by clicking "Add in new language" button
  • Go to Contacts tab and add at least "Support" and "Technical" contacts
  • On UI Information tab you will see some data extracted from metadata. Apart from those fill-in the rest
    • Keywords: university or research
    • For the tutorial put some dummy URL data for Information and Privacy Policy. But in production, you may have to provide your true data
  • On UI Hints tab you may add your DNS Domain as Also you may specify your IP blocks or Location
  • on SAML tab, tick the following on IDPSSODescriptor and AttributeAuthorityDescriptor? sections as Supported Name Identifiers
    • urn:oasis:names:tc:SAML:2.0:nameid-format:persistent
  • On Certificates tab, make sure it contains Certificate details, if not start Over by reloading IDP's metadata and pasting them.
  • Finally click Register.
  • Your Federation operator will review your application and will proceed with the registration
  1. Configure the IdP to retrieve the Federation Metadata:
  •    cd /opt/shibboleth-idp/conf
  •    vim metadata-providers.xml

Put the following provider details within the <MetadataProvider id="ShibbolethMetadata" xsi:type="ChainingMetadataProvider" ... ... </MetadataProvider> block.

                Verify the signature on the root element of the metadata aggregate
                using a trusted metadata signing certificate.
            <MetadataFilter xsi:type="SignatureValidation" requireSignedRoot="true" certificateFile="${idp.home}/metadata/federation-cert.pem"/>

                Require a validUntil XML attribute on the root element and
                make sure its value is no more than 10 days into the future.
            <MetadataFilter xsi:type="RequiredValidUntil" maxValidityInterval="P10D"/>

            <!-- Consume all SP metadata in the aggregate -->
            <MetadataFilter xsi:type="EntityRoleWhiteList">
  • Retrive the Federation Certificate used to verify its signed metadata:
  • wget -O /opt/shibboleth-idp/metadata/federation-cert.pem

  1. Reload service with id shibboleth.MetadataResolverService to retrieve the Federation Metadata:
  • cd /opt/shibboleth-idp/bin
  • ./ -id shibboleth.MetadataResolverService
  1. The day after the Federation Operators approve you, check whether your idp is listed under the institute list on following test services.

To be able to log-in, you should continue with the rest of the guide.

Configure Attribute Filters to release the mandatory attributes to the default LEARN Resources:

  1. Make sure that you have the "tmp/httpClientCache" used by "shibboleth.FileCachingHttpClient":
  •    mkdir -p /opt/shibboleth-idp/tmp/httpClientCache ; chown tomcat8 /opt/shibboleth-idp/tmp/httpClientCache
  1. Modify your services.xml:

   vim /opt/shibboleth-idp/conf/services.xml
  • Add following above the commented line <!-- This set of resources supports a native Spring relying-party.xml file. -->
      <bean id="Default-Filter" class="net.shibboleth.ext.spring.resource.FileBackedHTTPResource"
      <bean id="Production-Filter" class="net.shibboleth.ext.spring.resource.FileBackedHTTPResource"
  • Edit list shibboleth.AttributeFilterResources
      <util:list id ="shibboleth.AttributeFilterResources">
         <ref bean="Default-Filter"/>
         <ref bean="Production-Filter"/>
  1. Reload service with id shibboleth.AttributeFilterService to refresh the Attribute Filter followed by the IdP:
  • cd /opt/shibboleth-idp/bin
  • ./ -id shibboleth.AttributeFilterService

Enable Consent Module

The consent module is shown when a user logs in to a service for the first time, and asks the user for permission to release the required (and desired) attributes to the service.

  1. Edit /opt/shibboleth-idp/conf/ to uncomment and modify
     idp.consent.compareValues = true
     idp.consent.maxStoredRecords = -1
     idp.consent.storageRecordLifetime = P1Y

Restart the Tomcat service by service tomcat8 restart

  • By changing idp.consent.maxStoredRecords will remove the limit on the number of consent records held (by default, 10) by setting the limit to -1 (no limit)
  • The Storage Record Life Time of 1 year should be sufficient and the consent records would expire after a year.

Once you restart the service , the filters defined in step 38 will allow LEARN Federated Services to be authenticated with your IDP.

Release Attributes for your Service Providers (SP) in Production Environment

Edit /opt/shibboleth-idp/conf/attribute-filter.xml to include service providers who will use your IDP to authenticate your users for their services.

Consult Service Provider guidelines and on deciding what attributes you should release.

Reload shibboleth.AttributeFilterService to apply the new SP

Customization and Branding

The default install of the IdP login screen will display the Shibbolethlogo, a default prompt for username and password, and text saying that this screen should be customized. It is recommand to customize this page to have the proper institution logo and name. To give a consistent professional look, institution may customize the graphics to match the style of their,

  • login pages
  • onsent pages
  • logout pages
  • error pages

Those pages are created as Velocity template under /opt/shibboleth-idp/views

Therefore, it is recommended to customize the Velocity pages, adding supplementary images and CSS files as needed

Also the Velocity templates can be configured through message properties defined in message property files on /opt/shibboleth-idp/system/messages/ which should NOT be modified because of that, any customizations should be inserted into /opt/shibboleth-idp/messages/

least configurations:

idp.title - HTML TITLE to use across all of the IdP page templates. We recommend settings this to something like University of Example Login Service

idp.logo - relative path to the logo to render on the templates. E.g., /images/logo.jpg. The logo image has to be installed into /opt/shibboleth-idp/edit-webapp/images and the web application WAR file has to be rebuilt with /opt/shibboleth-idp/bin/

idp.logo.alt-text - the ALT text for your logo. Should be changed from the default value (where the text asks for the logo to be replaced).

idp.footer - footer that displays on (almost) all pages.

root.footer - footer that displays on some error pages.


idp.title = University of Example Login Service
idp.logo = /images/logo.jpg
idp.logo.alt-text = University of Example logo
idp.footer = Copyright University of Example
root.footer = Copyright University of Example

Depending on branding requirements, it may be sufficient to edit the CSS files in /opt/shibboleth-idp/edit-webapp/css, or it may be necessary to start editing the template pages.

Please note that the login page and most other pages use /opt/shibboleth-idp/edit-webapp/css/main.css, the consent module uses /opt/shibboleth-idp/edit-webapp/css/consent.css with different element names.

Besides the logo, the login page (and several other pages) display a toolbox on the right with placeholders for links to password-reset and help-desk pages, these can be customized by adding following to the /opt/shibboleth-idp/messages/

idp.url.password.reset =
idp.url.helpdesk =

Alternatively, it is also possible to hide the whole toolbox (the whole element) from all of the relevant pages (essentially, login.vm and all (three) logout pages: logout.vm, logout-complete.vm and logout.propagate). This can be easily done by adding the following CSS snippet into /opt/shibboleth-idp/edit-webapp/css/main.css:

.column.two {
    display: none;

For your simplisity in developing, temporary add the following to Apache idp-proxy.conf file ( /etc/apache2/sites-available/idp-proxy.conf ) to server the requests directly by Apache (avoiding going through Tomcat and thus avoiding having to rebuild the WAR file after every change):insert the following right above the ProxyPass? /idp directive:

ProxyPass /idp/images !
ProxyPass /idp/css !
Alias /idp/images /opt/shibboleth-idp/edit-webapp/images
Alias /idp/css /opt/shibboleth-idp/edit-webapp/css

And, as default permissions on Apache 2 are more restrictive, grant also explicitly access to the /opt/shibboleth-idp/edit-webapp directory: insert this at the very top of /etc/apache2/sites-available/idp-proxy.conf:

<Directory /opt/shibboleth-idp/edit-webapp>
   Require all granted

When done with changes to the images and css directories, remember to rebuild the WAR file and restart Tomcat:

service tomcat8 restart

Then remove the temporary additions on idp.conf and restart the apache service.

Appendix: Useful logs to find problems

Shibboleth installation is highly dependent on XML and Java syntaxes, if your server shows an error you should look for the top most error after the restart of the service.

  1. Tomcat 8 Logs:
  •    cd /var/log/tomcat8
  •    tail catalina.out
  1. Shibboleth IdP Logs:
  •    cd /opt/shibboleth-idp/logs
  • Audit Log: `tail idp-audit.log'
  • Consent Log: tail idp-consent-audit.log
  • Warn Log: tail idp-warn.log
  • Process Log: tail idp-process.log
  1. Apache Logs:
       cd /var/log/apache2/
  • Error Log: tail error.log
  • Access Log: tail access.log
Last modified 4 years ago Last modified on Jun 6, 2019, 12:56:41 PM