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


TABLE OF CONTENTS


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/upgrade

# Deploy changes in your repository to your IdP
/opt/shibboleth-idp-installer/repository/deploy

# Restart the IdP (Jetty)
systemctl restart idp


File system structure

The structure of the file system after a successful install is as follows: 


/opt
|--- jetty
| |--- jetty-distribution-9.4.31.v20200723
|--- shibboleth
|    |--- jetty
|    |--- libs
|    |--- shibboleth-idp
|    |    |--- shibboleth-idp-4.0.1
|    |--- shibboleth-src
|    |    |--- install-4.0.1.properties
|    |    |--- install-4.0.1.sh
|    |    |--- shibboleth-identity-provider-4.0.1
|--- shibboleth-idp4-installer
|    |--- activity.log
|    |--- build
|    |--- repository   

/var
|--- log
|    |--- jetty
|    |--- shibboleth-idp


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:        
      • /opt/shibboleth-idp4-installer
      • /opt/jetty
      • /opt/shibboleth
  • Monitor service availability
  • Monitor platform concerns, such as disk space and load averages, in particular the /var/log partition

Future Customisation

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