Operation

Following completion of all the previous stages the Shibboleth IdP enters an operational phase.

Administrators should be aware of the following concerns for the ongoing operation of the Shibboleth IdP.

Common commands

# Apply configuration changes to the IdP
/opt/shibboleth-idp-installer/repository/update_idp

# Restart the IdP (Jetty)
systemctl restart idp

# Restart apache
systemctl restart httpd

# Restart ntpd
systemctl restart ntpd

# Restart firewall
systemctl restart firewalld

Filesystem structure

The stucture of the filesystem after a successful install is as follows:

/opt
├── jetty
│   └── jetty-distribution-9.2.10.v20150310     # Jetty installation
├── keypairs                                    # TLS assets used for Apache
│   ├── intermediate.crt
│   ├── server.crt
│   └── server.key
├── shibboleth
│   ├── jetty                                   # Jetty base for Shib IdP
│   ├── shibboleth-idp
│   │   └── shibboleth-idp-3.1.1                # Shibboleth instance
│   └── shibboleth-src                          # Shib Installation files
│       ├── install-3.1.1.exp
│       ├── install-3.1.1.sh
│       └── shibboleth-identity-provider-3.1.1
└── shibboleth-idp-installer
    ├── repository                              # Holds configuration and source code
    └── build                                   # Working directory for installer

/var
└── log
    ├── shibboleth                              # Shibboleth specific logs
    ├── httpd                                   # Apache logs
    └── jetty                                   # Jetty base logs

Backup / Resilience

The IdP installer provides no backup or monitoring of the platform.

Deployers SHOULD:

Undertake regular backups of:
- The entire VM
- The local mariadb instance
- Key directories, including, but not limited to:
  1. /opt/shibboleth-idp-installer
  2. /opt/keypairs
  3. /opt/shibboleth
  4. /etc/httpd
Monitor service availability
Monitor platform concerns, such as disk space and load averages

Future Customisations

You can return to the customisation stage in the future to make further changes.