HOWTO Install and Configure a Shibboleth IdP v5.x on Debian-Ubuntu Linux with Apache + Jetty

Requirements
1. Hardware
2. Software
3. Others
Notes
Configure the environment
Configure APT Mirror
Install Dependencies
Install software requirements
1. Install Apache Web Server
2. Install Amazon Corretto JDK
3. Install Jetty Servlet Container
Install Shibboleth Identity Provider
Disable Jetty Directory Indexing
Configure Apache Web Server
Configure Jetty Context Descriptor for IdP
Configure Apache2 as the front-end of Jetty
Configure Shibboleth Identity Provider Storage Service
1. Strategy A - Default (HTML Local Storage, Encryption GCM, No Database) - Recommended
2. Strategy B - JDBC Storage Service - using a database
Configure the Directory Connection
1. openLDAP directory connection
2. Active Directory connection
Configure Shibboleth Identity Provider to release the persistent NameID
Configure the attribute resolver (sample)
Configure Shibboleth Identity Provider to release the eduPersonTargetedID
Configure Shibboleth IdP Logging
Translate IdP messages into preferred language
Enrich IdP Login Page with the Institutional Logo
Enrich IdP Login Page with Information and Privacy Policy pages
Change default login page footer text
Change default "Forgot your password?" and "Need help?" endpoints
Update IdP metadata
Secure cookies and other IDP data
Configure Attribute Filter Policy to release attributes to Federated Resources
Register the IdP on the IDEM Test Federation
Appendix A: Enable Consent Module (Attribute Release + Terms of Use Consent)
Appendix B: Useful logs to find problems
Appendix C: Connect an SP with the IdP
Appendix D: Javascript Engine
Appendix E: Enable F-Ticks logging
Utilities
Useful Documentation
Authors

Requirements

Hardware

CPU: 2 Core (64 bit)
RAM: 2 GB (with IDEM MDX), 4GB (without IDEM MDX)
HDD: 10 GB
OS: Debian (>= 13) / Ubuntu LTS (>= 24.04)

Software

Apache Web Server (>= 2.4)
Jetty 12.1.3+ Servlet Container (implementing Servlet API 5.0 or above)
Amazon Corretto JDK 17
OpenSSL (>= 3.5.1)
Shibboleth Identity Provider (>= 5.2.1)

Others

SSL Credentials: HTTPS Certificate & Private Key
Logo:
- size: 80x60 px (or other that respect the aspect-ratio)
- format: PNG
- style: with a transparent background
Favicon:
- size: 16x16 px (or other that respect the aspect-ratio)
- format: PNG
- style: with a transparent background

[TOC]

Notes

This HOWTO uses example.org and idp.example.org as example values.

Please remember to replace all occurencences of:

the example.org value with the IdP domain name
the idp.example.org value with the Full Qualified Domain Name of the Identity Provider.

[TOC]

Configure the environment

Become ROOT:
```
sudo su -
```
Be sure that your firewall is not blocking the traffic on port 443 and 80 for the IdP server.
Set the IdP hostname:

!!!ATTENTION!!!: Replace the label <YOUR-SERVER-IP-ADDRESS> with the IP address of the IdP server, the label idp.example.org with the IdP Full Qualified Domain Name value and the label <HOSTNAME> value with the IdP hostname value
- ```
echo "<YOUR-SERVER-IP-ADDRESS> idp.example.org <HOSTNAME>" >> /etc/hosts
```
- ```
hostnamectl set-hostname <HOSTNAME>
```

Configure the JAVA_HOME variable into /etc/environment:

echo 'JAVA_HOME=/usr/lib/jvm/java-17-amazon-corretto' > /etc/environment

```
source /etc/environment
```

export JAVA_HOME=/usr/lib/jvm/java-17-amazon-corretto

```
echo $JAVA_HOME
```

[TOC]

Configure APT Mirror

Debian Mirror List: https://www.debian.org/mirror/list

Ubuntu Mirror List: https://launchpad.net/ubuntu/+archivemirrors

Become ROOT:
```
sudo su -
```
Install package needed by mirrors protected by HTTPS:
```
apt update && apt install apt-transport-https
```

(only for italian institutions) Change the default mirror to the GARR one:

Debian example:

bash -c 'cat > /etc/apt/sources.list.d/garr.sources <<EOF
Types: deb
URIs: https://debian.mirror.garr.it/debian/
Suites: $(lsb_release -cs) $(lsb_release -cs)-updates $(lsb_release -cs)-backports
Components: main
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg

Types: deb
URIs: https://debian.mirror.garr.it/debian-security/
Suites: $(lsb_release -cs)-security
Components: main
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg
EOF'

Ubuntu example:

bash -c 'cat > /etc/apt/sources.list.d/garr.sources <<EOF
Types: deb
URIs: https://ubuntu.mirror.garr.it/ubuntu/
Suites: $(lsb_release -cs) $(lsb_release -cs)-updates $(lsb_release -cs)-backports
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg

Types: deb
URIs: https://ubuntu.mirror.garr.it/ubuntu-archive/
Suites: $(lsb_release -cs)-security
Components: main universe restricted multiverse
Signed-By: /usr/share/keyrings/ubuntu-archive-keyring.gpg
EOF'

Update packages:

apt update && apt-get upgrade -y --no-install-recommends

[TOC]

Install Dependencies

sudo apt install fail2ban vim wget gnupg ca-certificates openssl chrony --no-install-recommends

[TOC]

Install software requirements

Install Apache Web Server

The Apache HTTP Server will be configured as a reverse proxy and it will be used for SSL offloading.

sudo apt install apache2

[TOC]

Install Amazon Corretto JDK

Become ROOT:
```
sudo su -
```

Download the public key to verify package signatures from Amazon repository:

wget -O - https://apt.corretto.aws/corretto.key | sudo gpg --dearmor -o /usr/share/keyrings/corretto-keyring.gpg

Create an APT source list for Amazon Corretto:

bash -c 'cat > /etc/apt/sources.list.d/amazon-corretto.sources <<EOF
Types: deb
URIs: https://apt.corretto.aws
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/corretto-keyring.gpg

#Types: deb-src
#URIs: https://apt.corretto.aws
#Suites: stable
#Components: main
#Signed-By: /usr/share/keyrings/corretto-keyring.gpg
EOF'

Install Amazon Corretto:

apt update ; apt install -y java-17-amazon-corretto-jdk

Check that Java is working:
```
java --version
```
Result: OpenJDK Runtime Environment Corretto-<VERSION>

[TOC]

Install Jetty Servlet Container

Jetty is a Web server and a Java Servlet container. It will be used to run the IdP application through its WAR file.

Become ROOT:
```
sudo su -
```

Download and Extract Jetty 12 (take the latest version of jetty-home from the MAVEN website):

```
cd /usr/local/src
```

wget https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-home/12.1.5/jetty-home-12.1.5.tar.gz

```
tar xzvf jetty-home-12.1.5.tar.gz
```

Create the jetty-src folder as a symbolic link. It will be useful for future Jetty updates:
```
ln -nsf jetty-home-12.1.5 jetty-src
```
Create the system user jetty that can run the web server (without home directory):
```
useradd -r -M jetty
```

Create the custom Jetty configuration that overrides the default one and will survive upgrades:

```
mkdir -p /opt/jetty
```

wget https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/jetty-start.ini -O /opt/jetty/start.ini

(the start.ini provided is adapted to be used with IDEM MDX service)

Create the TMPDIR directory used by Jetty:

mkdir /opt/jetty/tmp ; chown jetty:jetty /opt/jetty/tmp

chown -R jetty:jetty /opt/jetty /usr/local/src/jetty-src

Create the Jetty Logs' folders:

```
mkdir /var/log/jetty
```
```
mkdir /opt/jetty/logs
```

chown jetty:jetty /var/log/jetty /opt/jetty/logs

Configure /etc/default/jetty:

bash -c 'cat > /etc/default/jetty <<EOF
JETTY_HOME=/usr/local/src/jetty-src
JETTY_BASE=/opt/jetty
JETTY_PID=/opt/jetty/jetty.pid
JETTY_USER=jetty
JETTY_START_LOG=/var/log/jetty/start.log
TMPDIR=/opt/jetty/tmp
EOF'

Create the service loadable from command line:

```
cd /etc/init.d
```

ln -s /usr/local/src/jetty-src/bin/jetty.sh jetty

sudo update-alternatives --config editor

(select /usr/bin/vim.basic as editor)

cp /usr/local/src/jetty-src/bin/jetty.service /etc/systemd/system/jetty.service

Fix the PIDFile parameter with the JETTY_PID path:

systemctl edit --full jetty.service

PIDFile=/opt/jetty/jetty.pid

```
systemctl daemon-reload
```
```
systemctl enable jetty.service
```

Install Servlet Jakarta API 5.0.0 needed to build and deploy the IdP WAR file:
- ```
apt install libjakarta-servlet-api-java
```

Install & configure LogBack for all Jetty logging:

```
cd /opt/jetty
```

java -jar /usr/local/src/jetty-src/start.jar --add-module=logging-logback

```
mkdir /opt/jetty/etc
```
```
mkdir /opt/jetty/resources
```

wget "https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/jetty-requestlog.xml" -O /opt/jetty/etc/jetty-requestlog.xml

wget "https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/jetty-logging.properties" -O /opt/jetty/resources/jetty-logging.properties

Check if all settings are OK:
- service jetty check (Jetty NOT running)
- service jetty start
- service jetty check (Jetty running pid=XXXX)
If you receive an error likes "Job for jetty.service failed because the control process exited with error code. See "systemctl status jetty.service" and "journalctl -xe" for details.", try this:
- ```
  rm /opt/jetty/jetty.pid
```
- ```
  systemctl start jetty.service
```

[TOC]

Install Shibboleth Identity Provider

The Identity Provider (IdP) is responsible for user authentication and providing user information to the Service Provider (SP). It is located at the home organization, which is the organization which maintains the,user's account. It is a Java Web Application that can be deployed with its WAR file.

Become ROOT:
```
sudo su -
```
Download the Shibboleth Identity Provider v5.x.y (replace '5.x.y' with the latest version found on the Shibboleth download site):
- ```
cd /usr/local/src
```
- ```
wget http://shibboleth.net/downloads/identity-provider/5.x.y/shibboleth-identity-provider-5.x.y.tar.gz
```

Validate the package downloaded:

```
cd /usr/local/src
```

wget https://shibboleth.net/downloads/identity-provider/5.x.y/shibboleth-identity-provider-5.x.y.tar.gz.asc

wget https://shibboleth.net/downloads/PGP_KEYS

```
gpg --import /usr/local/src/PGP_KEYS
```

gpg --verify /usr/local/src/shibboleth-identity-provider-5.x.y.tar.gz.asc /usr/local/src/shibboleth-identity-provider-5.x.y.tar.gz

If the result does not contain messages like gpg: BAD signature from ... the package is valid.

Extract the Shibboleth Identity Provider package:

tar -xzf shibboleth-identity-provider-5.*.tar.gz

Install Identity Provider Shibboleth:

NOTE

According to NSA and NIST, RSA with 3072 bit-modulus is the minimum to protect up to TOP SECRET over than 2030.

cd /usr/local/src/shibboleth-identity-provider-5.*/bin

bash install.sh --hostName $(hostname -f)

!!! ATTENTION !!!

Replace the default value of Attribute Scope with the domain name of your institution.

Installation Directory: [/opt/shibboleth-idp] ?                                        (Press ENTER)
SAML EntityID: [https://idp.example.org/idp/shibboleth] ?                              (Press ENTER)
Attribute Scope: [example.org] ?                            (Digit your domain name and press ENTER)

By starting from this point, the variable %{idp.home} into some IdP configuration files refers to the directory: /opt/shibboleth-idp

[TOC]

Disable Jetty Directory Indexing

!!! ATTENTION !!!

Jetty has had vulnerabilities related to directory indexing (sigh) so we suggest disabling that feature at this point.

Create missing directory:

mkdir /opt/shibboleth-idp/edit-webapp/WEB-INF

Fix web.xml:

cp /opt/shibboleth-idp/dist/webapp/WEB-INF/web.xml /opt/shibboleth-idp/edit-webapp/WEB-INF/web.xml

Rebuild IdP war file:
```
bash /opt/shibboleth-idp/bin/build.sh
```

[TOC]

Configure Apache Web Server

Create the DocumentRoot:

```
mkdir /var/www/html/$(hostname -f)
```

chown -R www-data: /var/www/html/$(hostname -f)

echo '<h1>It Works!</h1>' > /var/www/html/$(hostname -f)/index.html

Put SSL credentials in the right place:
- HTTPS Server Certificate (Public Key) inside /etc/ssl/certs/$(hostname -f).crt
- HTTPS Server Key (Private Key) inside /etc/ssl/private/$(hostname -f).key
- Add CA Cert into /etc/ssl/certs
  - If you use GARR TCS or GEANT TCS:
```
wget -O /etc/ssl/certs/GEANT_TLS_RSA_1.pem https://crt.sh/?d=16099180997
```
  - If you use ACME (Let's Encrypt):
```
ln -s /etc/letsencrypt/live/<SERVER_FQDN>/chain.pem /etc/ssl/certs/ACME-CA.pem
```
Configure the right privileges for the SSL Certificate and Key used by HTTPS:
- ```
chmod 400 /etc/ssl/private/$(hostname -f).key
```
- ```
chmod 644 /etc/ssl/certs/$(hostname -f).crt
```
($(hostname -f) will provide your IdP Full Qualified Domain Name)

Enable the required Apache2 modules and the virtual hosts:

a2enmod proxy_http ssl headers alias include negotiation

```
a2dissite 000-default.conf default-ssl
```
```
systemctl restart apache2.service
```

[TOC]

Configure Jetty Context Descriptor for IdP

Become ROOT:
```
sudo su -
```

Configure the Jetty Context Descriptor:

```
mkdir /opt/jetty/webapps
```

wget "https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/idp.xml" -O /opt/jetty/webapps/idp.xml

Make the jetty user owner of IdP main directories:

```
cd /opt/shibboleth-idp
```

chown -R jetty logs/ metadata/ credentials/ conf/ war/

Restart Jetty:
```
systemctl restart jetty.service
```

[TOC]

Configure Apache2 as the front-end of Jetty

The Apache HTTP Server will be configured as a reverse proxy and it will be used for SSL offloading.

Become ROOT:
```
sudo su -
```

Create the Virtualhost file:

wget https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/idp.example.org.conf -O /etc/apache2/sites-available/$(hostname -f).conf

(do not change idp.example.org with the FQDN of the IdP on the GitHub URL provided)

Edit the Virtualhost file (PLEASE PAY ATTENTION! you need to edit this file and customize it, check the initial comment of the file):
```
vim /etc/apache2/sites-available/$(hostname -f).conf
```

Enable the Apache2 virtual hosts created:

```
a2ensite $(hostname -f).conf
```
```
systemctl reload apache2.service
```

Check that IdP metadata is available on:

https://idp.example.org/idp/shibboleth
Verify the strength of your IdP's machine on SSLLabs.

[TOC]

Configure Shibboleth Identity Provider Storage Service

Shibboleth Documentation reference: StorageConfiguration

The IdP provides a number of general-purpose storage facilities that can be used by core subsystems like session management and consent.

Strategy A - Default (HTML Local Storage, Encryption GCM, No Database) - Recommended

The HTML Local Storage requires JavaScript be enabled because reading and writing to the client requires an explicit page be rendered. Note that this feature is safe to enable globally. The implementation is written to check for this capability in each client, and to back off to cookies. The default configuration generates encrypted assertions that a large percentage of non-Shibboleth SPs are going to be unable to decrypt, resulting a wide variety of failures and error messages. Some old Shibboleth SPs or software running on old Operating Systems will also fail to work.

!!! DO IT BECAUSE IT IS IMPORTANT !!!

(only for Italian Identity Federation IDEM members)

The IDEM Federation Operators collect a list of Service Providers that don't support the new default encryption algorithm and provide a solution on his wiki pages:

Idp4noGCMsps

If you don't change anything, the IdP stores data in a browser session cookie or HTML local storage and encrypt his assertions with AES-GCM encryption algorithm.

See the configuration files and the Shibboleth documentation for details.

Check IdP Status:

bash /opt/shibboleth-idp/bin/status.sh

Proceed with Configure the Directory Connection

[TOC]

Strategy B - JDBC Storage Service - using a database

https://shibboleth.atlassian.net/wiki/spaces/IDPPLUGINS/pages/2989096970/JDBCStorageService

This Storage service will memorize User Consent data on a persistent SQL database.

Become ROOT:
```
sudo su -
```

Install SQL database and needed libraries:

apt install default-mysql-server libmariadb-java libcommons-dbcp2-java libcommons-pool2-java --no-install-recommends

Install JDBCStorageService plugin:

/opt/shibboleth-idp/bin/plugin.sh -I net.shibboleth.plugin.storage.jdbc

Activate MariaDB database service:
```
systemctl start mariadb.service
```
Address several security concerns in a default MariaDB installation (if not already done):
```
mysql_secure_installation
```

(OPTIONAL) MySQL DB Access without password:

vim /root/.my.cnf

[client]
user=root
password=##ROOT-DB-PASSWORD-CHANGEME##

Create StorageRecords table on the storagerecords database:

wget https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/shib-sr-db.sql -O /root/shib-sr-db.sql

fill missing datas on the shib-sr-db.sql file before import:

```
mariadb < /root/shib-sr-db.sql
```
```
systemctl restart mariadb.service
```

Rebuild IdP war file with the needed libraries:

mkdir /opt/shibboleth-idp/edit-webapp/WEB-INF/lib

ln -s /usr/share/java/mariadb-java-client.jar /opt/shibboleth-idp/edit-webapp/WEB-INF/lib

ln -s /usr/share/java/commons-dbcp2.jar /opt/shibboleth-idp/edit-webapp/WEB-INF/lib

ln -s /usr/share/java/commons-pool2.jar /opt/shibboleth-idp/edit-webapp/WEB-INF/lib

```
bash /opt/shibboleth-idp/bin/build.sh
```

Configure JDBC Storage Service:

vim /opt/shibboleth-idp/conf/global.xml

and add the following directives to the tail, before the last </beans> tag:

<bean id="storagerecords.JDBCStorageService.DataSource"
      class="org.apache.commons.dbcp2.BasicDataSource" destroy-method="close" lazy-init="true"
      p:driverClassName="org.mariadb.jdbc.Driver"
      p:url="jdbc:mysql://localhost:3306/storagerecords?autoReconnect=true"
      p:username="###_SR-USERNAME-CHANGEME_###"
      p:password="###_SR-DB-USER-PASSWORD-CHANGEME_###"
      p:maxTotal="10"
      p:maxIdle="5"
      p:maxWaitMillis="15000"
      p:testOnBorrow="true"
      p:validationQuery="select 1"
      p:validationQueryTimeout="5" />

<bean id="storagerecords.JDBCStorageService" parent="shibboleth.JDBCStorageService"
      p:dataSource-ref="storagerecords.JDBCStorageService.DataSource" />

!!! IMPORTANT !!!:

remember to change "###_SR-USERNAME-CHANGEME_###" and "###_SR-DB-USER-PASSWORD-CHANGEME_###" with your DB user and password data.

Set the consent storage service to the JDBC storage service:

vim /opt/shibboleth-idp/conf/idp.properties

idp.consent.StorageService = storagerecords.JDBCStorageService

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure the Directory Connection

[TOC]

Configure the Directory Connection

openLDAP directory connection

Become ROOT:
```
sudo su -
```
Install useful packages:
```
apt install ldap-utils
```
Check that you can reach the Directory from your IDP server:
```
ldapsearch -x -H ldap://<LDAP-SERVER-FQDN-OR-IP> -D 'cn=idpuser,ou=system,dc=example,dc=org' -w '<IDPUSER-PASSWORD>' -b 'ou=people,dc=example,dc=org' '(uid=<USERNAME-USED-IN-THE-LOGIN-FORM>)'
```
- the baseDN (-b parameter) ==> ou=people,dc=example,dc=org (branch containing the registered users)
- the bindDN (-D parameter) ==> cn=idpuser,ou=system,dc=example,dc=org (distinguished name for the user that can made queries on the LDAP, read only is sufficient)
- the searchFilter (uid=<USERNAME-USED-IN-THE-LOGIN-FORM>) corresponds to the (uid=$resolutionContext.principal) searchFilter configured into conf/ldap.properties

Connect the openLDAP to the IdP to allow the authentication of the users:

Solution 1 - LDAP + STARTTLS:

Configure secrets.properties:

vim /opt/shibboleth-idp/credentials/secrets.properties

# Default access to LDAP authn and attribute stores.
idp.authn.LDAP.bindDNCredential              = ###IDPUSER_PASSWORD###
idp.attribute.resolver.LDAP.bindDNCredential = %{idp.authn.LDAP.bindDNCredential:undefined}

Configure ldap.properties:

The ldap.example.org have to be replaced with the FQDN of the LDAP server.

The idp.authn.LDAP.baseDN and idp.authn.LDAP.bindDN have to be replaced with the right value.

The property idp.attribute.resolver.LDAP.exportAttributes has to be added into the file and configured with the list of attributes the IdP retrieves directly from LDAP. The list MUST contain the attribute chosen for the persistent-id generation (idp.persistentId.sourceAttribute).

vim /opt/shibboleth-idp/conf/ldap.properties

idp.authn.LDAP.authenticator = bindSearchAuthenticator
idp.authn.LDAP.ldapURL = ldap://ldap.example.org
idp.authn.LDAP.useStartTLS = true
idp.authn.LDAP.sslConfig = certificateTrust
idp.authn.LDAP.trustCertificates = /opt/shibboleth-idp/credentials/ldap-server.crt

# List of attributes to request during authentication
idp.authn.LDAP.returnAttributes = passwordExpirationTime,loginGraceRemaining

idp.authn.LDAP.baseDN = ou=people,dc=example,dc=org
idp.authn.LDAP.subtreeSearch = false

# The userFilter is used to locate a directory entry to bind against for LDAP authentication.
idp.authn.LDAP.userFilter = (uid={user})

idp.authn.LDAP.bindDN = cn=idpuser,ou=system,dc=example,dc=org

# LDAP attribute configuration, see attribute-resolver.xml
# Note, this likely won't apply to the use of legacy V2 resolver configurations
idp.attribute.resolver.LDAP.ldapURL             = %{idp.authn.LDAP.ldapURL}
idp.attribute.resolver.LDAP.connectTimeout      = %{idp.authn.LDAP.connectTimeout:PT3S}
idp.attribute.resolver.LDAP.responseTimeout     = %{idp.authn.LDAP.responseTimeout:PT3S}
idp.attribute.resolver.LDAP.connectionStrategy  = %{idp.authn.LDAP.connectionStrategy:ACTIVE_PASSIVE}
idp.attribute.resolver.LDAP.baseDN              = %{idp.authn.LDAP.baseDN:undefined}
idp.attribute.resolver.LDAP.bindDN              = %{idp.authn.LDAP.bindDN:undefined}
idp.attribute.resolver.LDAP.useStartTLS         = %{idp.authn.LDAP.useStartTLS:true}
idp.attribute.resolver.LDAP.startTLSTimeout     = %{idp.authn.LDAP.startTLSTimeout:PT3S}
idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}

# The 'searchFilter' is used to find user attributes from an LDAP source
idp.attribute.resolver.LDAP.searchFilter        = (uid=$resolutionContext.principal)

# List of attributes produced by the Data Connector that should be directly exported as resolved IdPAttributes without requiring any <AttributeDefinition>
# The 'exportAttributes' contains a list space-separated of attributes to retrieve directly from the directory service.
idp.attribute.resolver.LDAP.exportAttributes    = uid cn sn givenName mail eduPersonAffiliation

Paste the OpenLDAP certificate into /opt/shibboleth-idp/credentials/ldap-server.crt.

Configure the right owner/group for the OpenLDAP certificate loaded:

chown jetty:root /opt/shibboleth-idp/credentials/ldap-server.crt ; chmod 600 /opt/shibboleth-idp/credentials/ldap-server.crt

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure Shibboleth Identity Provider to release the persistent NameID

Solution 2 - LDAP + TLS:

Configure secrets.properties:

vim /opt/shibboleth-idp/credentials/secrets.properties

# Default access to LDAP authn and attribute stores.
idp.authn.LDAP.bindDNCredential              = ###IDPUSER_PASSWORD###
idp.attribute.resolver.LDAP.bindDNCredential = %{idp.authn.LDAP.bindDNCredential:undefined}

Configure ldap.properties:

The ldap.example.org have to be replaced with the FQDN of the LDAP server.

The idp.authn.LDAP.baseDN and idp.authn.LDAP.bindDN have to be replaced with the right value.

vim /opt/shibboleth-idp/conf/ldap.properties

idp.authn.LDAP.authenticator = bindSearchAuthenticator
idp.authn.LDAP.ldapURL = ldaps://ldap.example.org
idp.authn.LDAP.useStartTLS = false
idp.authn.LDAP.sslConfig = certificateTrust
idp.authn.LDAP.trustCertificates = /opt/shibboleth-idp/credentials/ldap-server.crt

# List of attributes to request during authentication
idp.authn.LDAP.returnAttributes = pwdLastSet

idp.authn.LDAP.baseDN = ou=people,dc=example,dc=org
idp.authn.LDAP.subtreeSearch = false

# The userFilter is used to locate a directory entry to bind against for LDAP authentication.
idp.authn.LDAP.userFilter = (uid={user})

idp.authn.LDAP.bindDN = cn=idpuser,ou=system,dc=example,dc=org

# LDAP attribute configuration, see attribute-resolver.xml
# Note, this likely won't apply to the use of legacy V2 resolver configurations
idp.attribute.resolver.LDAP.ldapURL             = %{idp.authn.LDAP.ldapURL}
idp.attribute.resolver.LDAP.connectTimeout      = %{idp.authn.LDAP.connectTimeout:PT3S}
idp.attribute.resolver.LDAP.responseTimeout     = %{idp.authn.LDAP.responseTimeout:PT3S}
idp.attribute.resolver.LDAP.connectionStrategy  = %{idp.authn.LDAP.connectionStrategy:ACTIVE_PASSIVE}
idp.attribute.resolver.LDAP.baseDN              = %{idp.authn.LDAP.baseDN:undefined}
idp.attribute.resolver.LDAP.bindDN              = %{idp.authn.LDAP.bindDN:undefined}
idp.attribute.resolver.LDAP.useStartTLS         = %{idp.authn.LDAP.useStartTLS:true}
idp.attribute.resolver.LDAP.startTLSTimeout     = %{idp.authn.LDAP.startTLSTimeout:PT3S}
idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}

# The 'searchFilter' is used to find user attributes from an LDAP source
idp.attribute.resolver.LDAP.searchFilter        = (uid=$resolutionContext.principal)

# List of attributes produced by the Data Connector that should be directly exported as resolved IdPAttributes without requiring any <AttributeDefinition>
# The 'exportAttributes' contains a list space-separated of attributes to retrieve directly from the directory service.
idp.attribute.resolver.LDAP.exportAttributes    = uid cn sn givenName mail eduPersonAffiliation

Paste the content of AD-CA certificate into /opt/shibboleth-idp/credentials/AD-CA.crt

Configure the right owner/group to the OpenLDAP certificate loaded:

chown jetty:root /opt/shibboleth-idp/credentials/AD-CA.crt ; chmod 600 /opt/shibboleth-idp/credentials/AD-CA.crt

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure Shibboleth Identity Provider to release the persistent NameID

Solution 3 - plain LDAP:

Configure secrets.properties:

vim /opt/shibboleth-idp/credentials/secrets.properties

# Default access to LDAP authn and attribute stores.
idp.authn.LDAP.bindDNCredential              = ###IDPUSER_PASSWORD###
idp.attribute.resolver.LDAP.bindDNCredential = %{idp.authn.LDAP.bindDNCredential:undefined}

Configure ldap.properties:

The ldap.example.org have to be replaced with the FQDN of the LDAP server.

The idp.authn.LDAP.baseDN and idp.authn.LDAP.bindDN have to be replaced with the right value.

vim /opt/shibboleth-idp/conf/ldap.properties

idp.authn.LDAP.authenticator = bindSearchAuthenticator
idp.authn.LDAP.ldapURL = ldap://ldap.example.org
idp.authn.LDAP.useStartTLS = false

# List of attributes to request during authentication
idp.authn.LDAP.returnAttributes = passwordExpirationTime,loginGraceRemaining

idp.authn.LDAP.baseDN = ou=people,dc=example,dc=org
idp.authn.LDAP.subtreeSearch = false

# The userFilter is used to locate a directory entry to bind against for LDAP authentication.
idp.authn.LDAP.userFilter = (uid={user})

idp.authn.LDAP.bindDN = cn=idpuser,ou=system,dc=example,dc=org

# LDAP attribute configuration, see attribute-resolver.xml
# Note, this likely won't apply to the use of legacy V2 resolver configurations
idp.attribute.resolver.LDAP.ldapURL             = %{idp.authn.LDAP.ldapURL}
idp.attribute.resolver.LDAP.connectTimeout      = %{idp.authn.LDAP.connectTimeout:PT3S}
idp.attribute.resolver.LDAP.responseTimeout     = %{idp.authn.LDAP.responseTimeout:PT3S}
idp.attribute.resolver.LDAP.connectionStrategy  = %{idp.authn.LDAP.connectionStrategy:ACTIVE_PASSIVE}
idp.attribute.resolver.LDAP.baseDN              = %{idp.authn.LDAP.baseDN:undefined}
idp.attribute.resolver.LDAP.bindDN              = %{idp.authn.LDAP.bindDN:undefined}
idp.attribute.resolver.LDAP.useStartTLS         = %{idp.authn.LDAP.useStartTLS:true}
idp.attribute.resolver.LDAP.startTLSTimeout     = %{idp.authn.LDAP.startTLSTimeout:PT3S}
idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}

# The 'searchFilter' is used to find user attributes from an LDAP source
idp.attribute.resolver.LDAP.searchFilter        = (uid=$resolutionContext.principal)

# List of attributes produced by the Data Connector that should be directly exported as resolved IdPAttributes without requiring any <AttributeDefinition>
# The 'exportAttributes' contains a list space-separated of attributes to retrieve directly from the directory service.
idp.attribute.resolver.LDAP.exportAttributes    = uid cn sn givenName mail eduPersonAffiliation

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure Shibboleth Identity Provider to release the persistent NameID

[TOC]

Active Directory connection

Become ROOT:
```
sudo su -
```
Install useful packages:
```
apt install ldap-utils
```
Check that you can reach the Directory from your IDP server:
```
ldapsearch -x -H ldap://<AD-SERVER-FQDN-OR-IP> -D 'CN=idpuser,CN=Users,DC=ad,DC=example,DC=org' -w '<IDPUSER-PASSWORD>' -b 'CN=Users,DC=ad,DC=example,DC=org' '(sAMAccountName=<USERNAME-USED-IN-THE-LOGIN-FORM>)'
```
- the baseDN (-b parameter) ==> CN=Users,DC=ad,DC=example,DC=org (branch containing the registered users)
- the bindDN (-D parameter) ==> CN=idpuser,CN=Users,DC=ad,DC=example,DC=org (distinguished name for the user that can make queries on the LDAP, read only is sufficient)
- the searchFilter (sAMAccountName=<USERNAME-USED-IN-THE-LOGIN-FORM>) corresponds to the (sAMAccountName=$resolutionContext.principal) searchFilter configured into conf/ldap.properties
In the likely case Active Directory is set up to only accept secure LDAP queries, add the Certification Authority certificate (AD-CA certificate) to the IDP store, before the ldapsearch check. The AD-CA certificate is needed to verify that the certificates shown by the Domain Controllers/LDAPS servers are valid.

In short, the commands to add the certificate to the store are similar to:
```
sudo cp AD-CA.crt /usr/share/ca-certificates/mozilla
sudo dpkg-reconfigure ca-certificates
```
...and the check to reach the Directory, similar to:
```
ldapsearch -H ldaps://<LDAP-SERVER-FQDN-OR-IP>:636 -D username@example.org -W -b 'OU=People,DC=domain,DC=org' '(uid=<USERNAME-USED-IN-THE-LOGIN-FORM>)'
```
- the W parameter lets type the password instead to write in clear text in the command.
- the bindDN (-D parameter) ==> username@example.org is only an example and is used in another, more readable form.
A connectivity check can be done using any user with the same permissions

Connect the Active Directory to the IdP to allow the authentication of the users:

Solution 1 - AD + STARTTLS:

Configure secrets.properties:

vim /opt/shibboleth-idp/credentials/secrets.properties

# Default access to LDAP authn and attribute stores.
idp.authn.LDAP.bindDNCredential              = ###IDPUSER_PASSWORD###
idp.attribute.resolver.LDAP.bindDNCredential = %{idp.authn.LDAP.bindDNCredential:undefined}

Configure ldap.properties:

The ad.example.org have to be replaced with the FQDN of the AD server.

The idp.authn.LDAP.baseDN and idp.authn.LDAP.bindDN have to be replaced with the right value.

The property idp.attribute.resolver.LDAP.exportAttributes has to be added into the file and configured with the list of attributes the IdP retrieves directly from AD. The list MUST contain the attribute chosen for the persistent-id generation (idp.persistentId.sourceAttribute).

vim /opt/shibboleth-idp/conf/ldap.properties

idp.authn.LDAP.authenticator = bindSearchAuthenticator
idp.authn.LDAP.ldapURL = ldap://ad.example.org
idp.authn.LDAP.useStartTLS = true
idp.authn.LDAP.sslConfig = certificateTrust
idp.authn.LDAP.trustCertificates = /opt/shibboleth-idp/credentials/ad-server.crt

# List of attributes to request during authentication
idp.authn.LDAP.returnAttributes = passwordExpirationTime,loginGraceRemaining

idp.authn.LDAP.baseDN = CN=Users,DC=ad,DC=example,DC=org
idp.authn.LDAP.subtreeSearch = false

# The userFilter is used to locate a directory entry to bind against for AD authentication.
idp.authn.LDAP.userFilter = (sAMAccountName={user})

idp.authn.LDAP.bindDN = CN=idpuser,CN=Users,DC=ad,DC=example,DC=org

# LDAP attribute configuration, see attribute-resolver.xml
# Note, this likely won't apply to the use of legacy V2 resolver configurations
idp.attribute.resolver.LDAP.ldapURL             = %{idp.authn.LDAP.ldapURL}
idp.attribute.resolver.LDAP.connectTimeout      = %{idp.authn.LDAP.connectTimeout:PT3S}
idp.attribute.resolver.LDAP.responseTimeout     = %{idp.authn.LDAP.responseTimeout:PT3S}
idp.attribute.resolver.LDAP.connectionStrategy  = %{idp.authn.LDAP.connectionStrategy:ACTIVE_PASSIVE}
idp.attribute.resolver.LDAP.baseDN              = %{idp.authn.LDAP.baseDN:undefined}
idp.attribute.resolver.LDAP.bindDN              = %{idp.authn.LDAP.bindDN:undefined}
idp.attribute.resolver.LDAP.useStartTLS         = %{idp.authn.LDAP.useStartTLS:true}
idp.attribute.resolver.LDAP.startTLSTimeout     = %{idp.authn.LDAP.startTLSTimeout:PT3S}
idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}

# The 'searchFilter' is used to find user attributes from an LDAP source
idp.attribute.resolver.LDAP.searchFilter        = (sAMAccountName=$resolutionContext.principal)

# List of attributes produced by the Data Connector that should be directly exported as resolved IdPAttributes without requiring any <AttributeDefinition>
# The 'exportAttributes' contains a list space-separated of attributes to retrieve directly from the directory service.
idp.attribute.resolver.LDAP.exportAttributes    = sAMAccountName cn sn givenName mail eduPersonAffiliation

Paste the content of OpenLDAP certificate into /opt/shibboleth-idp/credentials/ad-server.crt

Configure the right owner/group to the OpenLDAP certificate loaded:

chown jetty:root /opt/shibboleth-idp/credentials/ad-server.crt ; chmod 600 /opt/shibboleth-idp/credentials/ad-server.crt

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure Shibboleth Identity Provider to release the persistent NameID

Solution 2: AD + TLS:

Configure secrets.properties:

vim /opt/shibboleth-idp/credentials/secrets.properties

# Default access to LDAP authn and attribute stores.
idp.authn.LDAP.bindDNCredential              = ###IDPUSER_PASSWORD###
idp.attribute.resolver.LDAP.bindDNCredential = %{idp.authn.LDAP.bindDNCredential:undefined}

Configure ldap.properties:

The ad.example.org have to be replaced with the FQDN of the AD server.

The idp.authn.LDAP.baseDN and idp.authn.LDAP.bindDN have to be replaced with the right value.

vim /opt/shibboleth-idp/conf/ldap.properties

idp.authn.LDAP.authenticator = bindSearchAuthenticator
idp.authn.LDAP.ldapURL = ldaps://ad.example.org
idp.authn.LDAP.useStartTLS = false
idp.authn.LDAP.sslConfig = certificateTrust
idp.authn.LDAP.trustCertificates = /opt/shibboleth-idp/credentials/ad-server.crt

# List of attributes to request during authentication
idp.authn.LDAP.returnAttributes = passwordExpirationTime,loginGraceRemaining

idp.authn.LDAP.baseDN = CN=Users,DC=ad,DC=example,DC=org
idp.authn.LDAP.subtreeSearch = false

# The userFilter is used to locate a directory entry to bind against for AD authentication.
idp.authn.LDAP.userFilter = (sAMAccountName={user})

idp.authn.LDAP.bindDN = CN=idpuser,CN=Users,DC=ad,DC=example,DC=org

# LDAP attribute configuration, see attribute-resolver.xml
# Note, this likely won't apply to the use of legacy V2 resolver configurations
idp.attribute.resolver.LDAP.ldapURL             = %{idp.authn.LDAP.ldapURL}
idp.attribute.resolver.LDAP.connectTimeout      = %{idp.authn.LDAP.connectTimeout:PT3S}
idp.attribute.resolver.LDAP.responseTimeout     = %{idp.authn.LDAP.responseTimeout:PT3S}
idp.attribute.resolver.LDAP.connectionStrategy  = %{idp.authn.LDAP.connectionStrategy:ACTIVE_PASSIVE}
idp.attribute.resolver.LDAP.baseDN              = %{idp.authn.LDAP.baseDN:undefined}
idp.attribute.resolver.LDAP.bindDN              = %{idp.authn.LDAP.bindDN:undefined}
idp.attribute.resolver.LDAP.useStartTLS         = %{idp.authn.LDAP.useStartTLS:true}
idp.attribute.resolver.LDAP.startTLSTimeout     = %{idp.authn.LDAP.startTLSTimeout:PT3S}
idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}

# The 'searchFilter' is used to find user attributes from an LDAP source
idp.attribute.resolver.LDAP.searchFilter        = (sAMAccountName=$resolutionContext.principal)

# List of attributes produced by the Data Connector that should be directly exported as resolved IdPAttributes without requiring any <AttributeDefinition>
# The 'exportAttributes' contains a list space-separated of attributes to retrieve directly from the directory service.
idp.attribute.resolver.LDAP.exportAttributes    = sAMAccountName cn sn givenName mail eduPersonAffiliation

Paste the content of OpenLDAP certificate into /opt/shibboleth-idp/credentials/ad-server.crt

Configure the right owner/group to the OpenLDAP certificate loaded:

chown jetty:root /opt/shibboleth-idp/credentials/ad-server.crt ; chmod 600 /opt/shibboleth-idp/credentials/ad-server.crt

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure Shibboleth Identity Provider to release the persistent NameID

Solution 3 - plain AD:

Configure secrets.properties:

vim /opt/shibboleth-idp/credentials/secrets.properties

# Default access to LDAP authn and attribute stores.
idp.authn.LDAP.bindDNCredential              = ###IDPUSER_PASSWORD###
idp.attribute.resolver.LDAP.bindDNCredential = %{idp.authn.LDAP.bindDNCredential:undefined}

Configure ldap.properties:

The ad.example.org have to be replaced with the FQDN of the AD server.

The idp.authn.LDAP.baseDN and idp.authn.LDAP.bindDN have to be replaced with the right value.

vim /opt/shibboleth-idp/conf/ldap.properties

idp.authn.LDAP.authenticator = bindSearchAuthenticator
idp.authn.LDAP.ldapURL = ldap://ad.example.org
idp.authn.LDAP.useStartTLS = false

# List of attributes to request during authentication
idp.authn.LDAP.returnAttributes = passwordExpirationTime,loginGraceRemaining

idp.authn.LDAP.baseDN = CN=Users,DC=ad,DC=example,DC=org
idp.authn.LDAP.subtreeSearch = false

# The userFilter is used to locate a directory entry to bind against for AD authentication.
idp.authn.LDAP.userFilter = (sAMAccountName={user})

idp.authn.LDAP.bindDN = CN=idpuser,CN=Users,DC=ad,DC=example,DC=org

# LDAP attribute configuration, see attribute-resolver.xml
# Note, this likely won't apply to the use of legacy V2 resolver configurations
idp.attribute.resolver.LDAP.ldapURL             = %{idp.authn.LDAP.ldapURL}
idp.attribute.resolver.LDAP.connectTimeout      = %{idp.authn.LDAP.connectTimeout:PT3S}
idp.attribute.resolver.LDAP.responseTimeout     = %{idp.authn.LDAP.responseTimeout:PT3S}
idp.attribute.resolver.LDAP.connectionStrategy  = %{idp.authn.LDAP.connectionStrategy:ACTIVE_PASSIVE}
idp.attribute.resolver.LDAP.baseDN              = %{idp.authn.LDAP.baseDN:undefined}
idp.attribute.resolver.LDAP.bindDN              = %{idp.authn.LDAP.bindDN:undefined}
idp.attribute.resolver.LDAP.useStartTLS         = %{idp.authn.LDAP.useStartTLS:true}
idp.attribute.resolver.LDAP.startTLSTimeout     = %{idp.authn.LDAP.startTLSTimeout:PT3S}
idp.attribute.resolver.LDAP.trustCertificates   = %{idp.authn.LDAP.trustCertificates:undefined}

# The 'searchFilter' is used to find user attributes from an LDAP source
idp.attribute.resolver.LDAP.searchFilter        = (sAMAccountName=$resolutionContext.principal)

# List of attributes produced by the Data Connector that should be directly exported as resolved IdPAttributes without requiring any <AttributeDefinition>
# The 'exportAttributes' contains a list space-separated of attributes to retrieve directly from the directory service.
idp.attribute.resolver.LDAP.exportAttributes    = sAMAccountName cn sn givenName mail eduPersonAffiliation

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```
Proceed with Configure Shibboleth Identity Provider to release the persistent NameID

[TOC]

Configure Shibboleth Identity Provider to release the persistent NameID

DOC: PersistentNameIDGenerationConfiguration

SAML 2.0 (but not SAML 1.x) defines a kind of NameID called a "persistent" identifier that every SP receives for the IdP users. This part will teach you how to release the "persistent" identifiers with a database (Stored Mode) or without it (Computed Mode).

By default, a transient NameID will always be released to the Service Provider if the persistent one is not requested.

Become ROOT:
```
sudo su -
```

Enable the generation of the computed persistent-id with:

vim /opt/shibboleth-idp/conf/saml-nameid.properties

The sourceAttribute MUST be an attribute, or a list of comma-separated attributes, that uniquely identify the subject of the generated persistent-id.

The sourceAttribute MUST reference one or more Stable, Permanent and Not-reassignable attributes supported by the IdP Attribute Resolver.

# ... other things ...#
# OpenLDAP has the UserID into "uid" attribute
idp.persistentId.sourceAttribute = uid

# Active Directory has the UserID into "sAMAccountName"
#idp.persistentId.sourceAttribute = sAMAccountName
# ... other things ...#

vim /opt/shibboleth-idp/conf/saml-nameid.xml

Uncomment the line:

<ref bean="shibboleth.SAML2PersistentGenerator" />

vim /opt/shibboleth-idp/credentials/secrets.properties

idp.persistentId.salt = ### result of command 'openssl rand -base64 36' ###

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```

[TOC]

Configure the attribute resolver (sample)

The attribute resolver contains attribute definitions and data connectors that collect information from a variety of sources, combine and transform it, and produce a final collection of IdPAttribute objects, which are an internal representation of user data not specific to SAML or any other supported identity protocol.

Become ROOT:
```
sudo su -
```

Download the sample attribute resolver provided by IDEM GARR AAI Federation Operators (OpenLDAP / Active Directory compliant):

wget https://conf.idem.garr.it/idem-attribute-resolver-shib-v5.xml -O /opt/shibboleth-idp/conf/attribute-resolver.xml

If you decide to use the plain text LDAP/AD solution, remove or comment the following directives from your Attribute Resolver file:

Line 1:  useStartTLS="%{idp.attribute.resolver.LDAP.useStartTLS:true}"
Line 2:  trustFile="%{idp.attribute.resolver.LDAP.trustCertificates}"

Configure the right owner:

chown jetty /opt/shibboleth-idp/conf/attribute-resolver.xml

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```

[TOC]

Configure Shibboleth Identity Provider to release the eduPersonTargetedID

eduPersonTargetedID is an abstracted version of the SAML V2.0 Name Identifier format of urn:oasis:names:tc:SAML:2.0:nameid-format:persistent.

To be able to follow these steps, you need to have followed the previous steps on persistent NameID generation.

Become ROOT:
```
sudo su -
```

Check to have the following <AttributeDefinition> and the <DataConnector> into the attribute-resolver.xml:

vim /opt/shibboleth-idp/conf/attribute-resolver.xml

<!-- ...other things ... -->

<!--  AttributeDefinition for eduPersonTargetedID - Computed Mode  -->
<!--
      WARN [DEPRECATED:173] - xsi:type 'SAML2NameID'
      This feature is at-risk for removal in a future version

      NOTE: eduPersonTargetedID is DEPRECATED and should not be used.
-->
<AttributeDefinition xsi:type="SAML2NameID" nameIdFormat="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" id="eduPersonTargetedID">
    <InputDataConnector ref="computed" attributeNames="computedId" />
</AttributeDefinition>

<!-- ... other things... -->

<!--  Data Connector for eduPersonTargetedID - Computed Mode  -->

<DataConnector id="computed" xsi:type="ComputedId"
    generatedAttributeID="computedId"
    salt="%{idp.persistentId.salt}"
    algorithm="%{idp.persistentId.algorithm:SHA}"
    encoding="%{idp.persistentId.encoding:BASE32}">

    <InputDataConnector ref="myLDAP" attributeNames="%{idp.persistentId.sourceAttribute}" />

</DataConnector>

Create the custom eduPersonTargetedID.properties file:

wget https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/eduPersonTargetedID.properties -O /opt/shibboleth-idp/conf/attributes/custom/eduPersonTargetedID.properties

Set proper owner/group with:

chown jetty:root /opt/shibboleth-idp/conf/attributes/custom/eduPersonTargetedID.properties

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```

[TOC]

Configure Shibboleth IdP Logging

Become ROOT:
```
sudo su -
```

Enrich IDP logs with the authentication error occurred on LDAP:

sed -i '/^    <logger name="org.ldaptive".*/a \\n    <!-- Logs on LDAP user authentication - ADDED BY IDEM HOWTO -->' /opt/shibboleth-idp/conf/logback.xml

sed -i '/^    <!-- Logs on LDAP user authentication - ADDED BY IDEM HOWTO -->/a \ \ \ \ \<logger name="org.ldaptive.auth.Authenticator" level="INFO" />' /opt/shibboleth-idp/conf/logback.xml

[TOC]

Translate IdP messages into preferred language

Translate the IdP messages in your language:

Get the files translated in your language from MessagesTranslation
Put messages_XX.properties downloaded file into /opt/shibboleth-idp/messages directory
Restart Jetty to apply the changes with systemctl restart jetty.service

[TOC]

Enrich IdP Login Page with the Institutional Logo

Discover what images are publicly available by opening an URL similar to "https://idp.example.org/idp/images/" from a web browser.
Copy the institutional logo into all placeholder found inside the /opt/shibboleth-idp/edit-webapp/images directory without renaming them.
Rebuild IdP war file:
```
bash /opt/shibboleth-idp/bin/build.sh
```
Restart Jetty:
```
sudo systemctl restart jetty.service
```

[TOC]

Enrich IdP Login Page with Information and Privacy Policy pages

Add the following two lines into views/login.vm:

<li class="list-help-item"><a href="#springMessageText("idp.url.infoPage", '#')"><span class="item-marker">&rsaquo;</span> #springMessageText("idp.login.infoPage", "Information page")</a></li>
<li class="list-help-item"><a href="#springMessageText("idp.url.privacyPage", '#')"><span class="item-marker">&rsaquo;</span> #springMessageText("idp.login.privacyPage", "Privacy Policy")</a></li>

under the line containing the Anchor:

<a href="#springMessageText("idp.url.helpdesk", '#')">

Add the new variables defined with lines added at point 1 into all messages*.properties files linked to the view view/login.vm:

Move to the IdP Home:
```
cd /opt/shibboleth-idp
```

Modify messages.properties:

vim messages/messages.properties

idp.login.infoPage=Informations
idp.url.infoPage=https://idp.example.org/english-idp-info-page.html
idp.login.privacyPage=Privacy Policy
idp.url.privacyPage=https://idp.example.org/english-idp-privacy-policy.html

Modify messages_it.properties:

vim messages/messages_it.properties

idp.login.infoPage=Informazioni
idp.url.infoPage=https://idp.example.org/italian-idp-info-page.html
idp.login.privacyPage=Privacy Policy
idp.url.privacyPage=https://idp.example.org/italian-idp-privacy-policy.html

Rebuild IdP WAR file and Restart Jetty to apply changes:

```
bash /opt/shibboleth-idp/bin/build.sh
```
```
sudo systemctl restart jetty
```

[TOC]

Change default login page footer text

Change the content of idp.footer variable into all messages*.properties files linked to the view view/login.vm:

```
  cd /opt/shibboleth-idp
```

  vim messages/messages.properties

idp.footer=Footer text for english version of IdP login page

  vim messages/messages_it.properties:

idp.footer=Testo del Footer a pie di pagina per la versione italiana della pagina di login dell'IdP

[TOC]

Change default "Forgot your password?" and "Need help?" endpoints

Change the content of idp.url.password.reset and idp.url.helpdesk variables into messages*.properties files linked to the view view/login.vm:

Move to the IdP Home:
```
cd /opt/shibboleth-idp
```

Modify messages.properties:

vim messages/messages.properties

idp.url.password.reset=###ENGLISH-FORGOT-YOUR-PASSWORD-LINK###
idp.url.helpdesk=###ENGLISH-NEED-HELP-LINK###

Modify messages_it.properties:

vim messages/messages_it.properties

idp.url.password.reset=CONTENUTO-PER-LINK-PASSWORD-DIMENTICATA
idp.url.helpdesk=CONTENUTO-PER-SERVE-AIUTO-LINK

[TOC]

Update IdP metadata

(only for italian identity federation IDEM members)

Modify the IdP metadata as follow:
```
vim /opt/shibboleth-idp/metadata/idp-metadata.xml
```
1. Remove completely the initial default comment
2. Remove completely the comment containing <mdui:UIInfo> element from <IDPSSODescriptor> Section.
3. Add the HTTP-Redirect SingleLogoutService endpoints under the SOAP one:
```
<md:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="https://idp.example.org/idp/profile/SAML2/Redirect/SLO"/>
```
  (replace idp.example.org value with the Full Qualified Domain Name of the Identity Provider.)
4. Between the last <SingleLogoutService> and the first <SingleSignOnService> endpoints add:
```
<md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:transient</md:NameIDFormat>
<md:NameIDFormat>urn:oasis:names:tc:SAML:2.0:nameid-format:persistent</md:NameIDFormat>
```
  (because the IdP installed with this guide will release transient NameID, by default, and persistent NameID if requested.)
Check that the metadata is available on /idp/shibboleth location:

https://idp.example.org/idp/shibboleth

[TOC]

Secure cookies and other IDP data

DOC: SecretKeyManagement

The default configuration of the IdP relies on a component called a "DataSealer" which in turn uses an AES secret key to secure cookies and certain other data for the IdPs own use. This key must never be shared with anybody else, and must be copied to every server node making up a cluster. The Java "JCEKS" keystore file stores secret keys instead of public/private keys and certificates and a parallel file tracks the key version number.

These instructions will regularly update the secret key (and increase its version) and provide you the capability to push it to cluster nodes and continually maintain the secrecy of the key.

Download updateIDPsecrets.sh into the right location:

wget https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/updateIDPsecrets.sh -O /opt/shibboleth-idp/bin/updateIDPsecrets.sh

Provide the right privileges to the script:

sudo chmod +x /opt/shibboleth-idp/bin/updateIDPsecrets.sh

Install Cron:
```
sudo apt install cron
```

Create the CRON script to run it:

sudo vim /etc/cron.daily/updateIDPsecrets

#!/bin/bash

/opt/shibboleth-idp/bin/updateIDPsecrets.sh

Provide the right privileges to the script:

sudo chmod +x /etc/cron.daily/updateIDPsecrets

Confirm that the script will be run daily with (you should see your script in the command output):
```
sudo run-parts --test /etc/cron.daily
```
(OPTIONAL) Add the following properties to conf/idp.properties if you need to set different values than defaults:
- idp.sealer._count - Number of earlier keys to keep (default "30")
- idp.sealer._sync_hosts - Space separated list of hosts to scp the sealer files to (default generate locally)

[TOC]

Configure Attribute Filter Policy to release attributes to Federated Resources

Follow these steps ONLY IF your organization is connected to the GARR Network.

Become ROOT:
```
sudo su -
```

Create the directory tmp/httpClientCache used by shibboleth.FileCachingHttpClient:

mkdir -p /opt/shibboleth-idp/tmp/httpClientCache ; chown jetty /opt/shibboleth-idp/tmp/httpClientCache

Modify your services.xml:

vim /opt/shibboleth-idp/conf/services.xml

and add the following two beans on the top of the file, under the first <beans> TAG, only one time:

<bean id="MyHTTPClient" parent="shibboleth.FileCachingHttpClientFactory"
      p:connectionTimeout="PT30S"
      p:connectionRequestTimeout="PT30S"
      p:socketTimeout="PT30S"
      p:cacheDirectory="%{idp.home}/tmp/httpClientCache" />

<bean id="IdemAttributeFilterFull" class="net.shibboleth.ext.spring.resource.FileBackedHTTPResource"
      c:client-ref="MyHTTPClient"
      c:url="https://conf.idem.garr.it/idem-attribute-filter-shib-v5-full.xml"
      c:backingFile="%{idp.home}/conf/idem-attribute-filter-full.xml"/>

and enrich the AttributeFilterResources list with IdemAttributeFilterFull:

<!-- ...other things... -->

<util:list id ="shibboleth.AttributeFilterResources">
    <value>%{idp.home}/conf/attribute-filter.xml</value>
    <ref bean="IdemAttributeFilterFull"/>
</util:list>

<!-- ...other things... -->

Restart Jetty to apply the changes:
```
systemctl restart jetty.service
```
Check IdP Status:
```
bash /opt/shibboleth-idp/bin/status.sh
```

[TOC]

Register the IdP on the IDEM Test Federation

Follow these steps ONLY IF your organization is connected to the GARR Network.

Register you IdP metadata on IDEM Entity Registry (your entity have to be approved by an IDEM Federation Operator before become part of IDEM Test Federation):

https://registry.idem.garr.it/
Configure the IdP to retrieve the Federation Metadata through IDEM MDX: https://mdx.idem.garr.it/
Check that your IdP release at least eduPersonScopedAffiliation, eduPersonTargetedID and a saml2:NameID transient/persistent to the testing SP provided by IDEM:
```
bash /opt/shibboleth-idp/bin/aacli.sh -n <USERNAME> -r https://sp.example.org/shibboleth --saml2
```
(the command will have a transient NameID into the Subject of the assertion)
```
bash /opt/shibboleth-idp/bin/aacli.sh -n <USERNAME> -r https://sp.aai-test.garr.it/shibboleth --saml2
```
(the command will have a persistent NameID into the Subject of the assertion)
Wait that your IdP Metadata is approved by an IDEM Federation Operator into the IDEM Test Federation metadata stream and the next steps provided by the operator itself.

[TOC]

Appendix A: Enable Consent Module (Attribute Release + Terms of Use Consent)

DOC: ConsentConfiguration

The IdP includes the ability to require user consent to attribute release, as well as presenting a "terms of use" message prior to completing a login to a service, a simpler "static" form of consent.

Move to IdP home dir:
```
cd /opt/shibboleth-idp
```

Load Consent Module:

bin/module.sh -t idp.intercept.Consent || bin/module.sh -e idp.intercept.Consent

Enable Consent Module by editing the DefaultRelyingParty on conf/relying-party.xml with the right postAuthenticationFlows:
- <bean parent="SAML2.SSO" p:postAuthenticationFlows="attribute-release" /> - to enable only Attribute Release Consent
- <bean parent="SAML2.SSO" p:postAuthenticationFlows="#{ {'terms-of-use', 'attribute-release'} }" /> - to enable both
(instead of <ref bean="SAML2.SSO" />)
Restart Jetty:
```
sudo systemctl restart jetty.service
```

[TOC]

Appendix B: Useful logs to find problems

Follow this if you need to find a problem of your IdP.

Jetty Logs:

cd /opt/jetty/logs

ls -l *.stderrout.log

Shibboleth IdP Logs:
```
cd /opt/shibboleth-idp/logs
```
- Audit Log: vim idp-audit.log
- Consent Log: vim idp-consent-audit.log
- Warn Log: vim idp-warn.log
- Process Log: vim idp-process.log

[TOC]

Appendix C: Connect an SP with the IdP

DOC:

Follow these steps IF your organization IS NOT connected to the GARR Network.

Connect the SP to the IdP by adding its metadata on the metadata-providers.xml configuration file:

vim /opt/shibboleth-idp/conf/metadata-providers.xml

<MetadataProvider id="HTTPMetadata"
                  xsi:type="FileBackedHTTPMetadataProvider"
                  backingFile="%{idp.home}/metadata/sp-metadata.xml"
                  metadataURL="https://sp.example.org/Shibboleth.sso/Metadata"
                  failFastInitialization="false"/>

Adding an AttributeFilterPolicy on the conf/attribute-filter.xml file:
- ```
  wget https://github.com/ConsortiumGARR/idem-tutorials/raw/master/idem-fedops/HOWTO-Shibboleth/Identity%20Provider/utils/idem-example-arp.txt -O /opt/shibboleth-idp/conf/example-arp.txt
```
- ```
  cat /opt/shibboleth-idp/conf/example-arp.txt
```
- Copy and paste the content into /opt/shibboleth-idp/conf/attribute-filter.xml before the last element </AttributeFilterPolicyGroup>.
- Make sure to change the value of the placeholder ### SP-ENTITYID ### on the text pasted with the entityID of the Service Provider to connect with the Identity Provider installed.
Restart Jetty to apply changes:
```
systemctl restart jetty
```

[TOC]

Appendix D: Javascript Engine

DOC:

The Nashorn plugin provides support for the Nashorn JavaScript engine for IdPs of version 4.1 and beyond. This the scripting engine that was shipped with Java between versions 8 to 14 (it is not present as of JDK15).

Follow these steps IF you have to use ScriptedAttributeDefinition in the attribute-resolver.xml file:

Move into the IdP bin directory:
```
cd /opt/shibboleth/bin
```

Install Nashorn:

./plugin.sh -I net.shibboleth.idp.plugin.nashorn

[TOC]

Appendix E: Enable F-Ticks logging

(only for italian institutions)

Configure the IdP to send F-Ticks log to the IDEM GARR Federation:

https://conf.idem.garr.it/en/fticks/#shibboleth-identity-provider-configuration

Utilities

AACLI: Useful to understand which attributes will be released to the federated resources
- export JAVA_HOME=/usr/lib/jvm/java-17-amazon-corretto
- bash /opt/shibboleth-idp/bin/aacli.sh -n <USERNAME> -r <ENTITYID-SP> --saml2
The Mozilla Observatory: The Mozilla Observatory has helped over 240,000 websites by teaching developers, system administrators, and security professionals how to configure their sites safely and securely.

[TOC]

Useful Documentation

[TOC]

Authors

Original Author

Marco Malavolti (marco.malavolti@garr.it)

[TOC]

FilesExpand file tree

HOWTO-Install-and-Configure-a-Shibboleth-IdP-v5.x-on-Debian-Ubuntu-Linux-with-Apache-+-Jetty.md

Latest commit

History

HOWTO-Install-and-Configure-a-Shibboleth-IdP-v5.x-on-Debian-Ubuntu-Linux-with-Apache-+-Jetty.md

File metadata and controls

HOWTO Install and Configure a Shibboleth IdP v5.x on Debian-Ubuntu Linux with Apache + Jetty

Table of Contents

Requirements

Hardware

Software

Others

Notes

Configure the environment

Configure APT Mirror

Install Dependencies

Install software requirements

Install Apache Web Server

Install Amazon Corretto JDK

Install Jetty Servlet Container

Install Shibboleth Identity Provider

Disable Jetty Directory Indexing

Configure Apache Web Server

Configure Jetty Context Descriptor for IdP

Configure Apache2 as the front-end of Jetty

Configure Shibboleth Identity Provider Storage Service

Strategy A - Default (HTML Local Storage, Encryption GCM, No Database) - Recommended

Strategy B - JDBC Storage Service - using a database

Configure the Directory Connection

openLDAP directory connection

Active Directory connection

Configure Shibboleth Identity Provider to release the persistent NameID

Configure the attribute resolver (sample)

Configure Shibboleth Identity Provider to release the eduPersonTargetedID

Configure Shibboleth IdP Logging

Translate IdP messages into preferred language

Enrich IdP Login Page with the Institutional Logo

Enrich IdP Login Page with Information and Privacy Policy pages

Change default login page footer text

Change default "Forgot your password?" and "Need help?" endpoints

Update IdP metadata

Secure cookies and other IDP data

Configure Attribute Filter Policy to release attributes to Federated Resources

Register the IdP on the IDEM Test Federation

Appendix A: Enable Consent Module (Attribute Release + Terms of Use Consent)

Appendix B: Useful logs to find problems

Appendix C: Connect an SP with the IdP

Appendix D: Javascript Engine

Appendix E: Enable F-Ticks logging

Utilities

Useful Documentation

Authors

Original Author