...
Full Reference
- A full reference to all the options and settings can be reached by starting at the
<SPConfig>root topic, which is the element at the root of the shibboleth2.xml file, the core configuration
...
- file.
Installation Layout
The following summary will guide you in understanding the installed software layout and how to locate important files. The layout will be mostly familiar to those experienced with Linux/Unix software. The exact directories will vary based on how the installation is done and the system CPU architecture. On Windows there are both 32-bit and 64-bit files on a 64-bit OS.
...
| sbin[64] | "System"-level executable programs, e.g. the shibd daemon lives here |
| bin[64] | Contains some command line programs, and some general utilities (e.g. openssl and curl on Windows) |
| lib[64] | May contain libraries included with the software if not installed in a more general location. |
| lib[64]/shibboleth | Plugins and web server modules |
| etc/shibboleth | Contains most/all of the SP's configuration files, templates, and example scripts. Genrally "live" web server configuration is not here but examples may be. This is also typically where the SP's private key and certificate credentials are located, and is where certificates used to verify signed metadata are placed. During any installation (first time or upgrades), modified files are never replaced in this directory. New files required by the SP version being installed will be populated if and only if they do not exist. Generally each packaging mechanism we support is programmed to do the reasonable thing within its capabilities to keep systems working properly. Copies of the original versions of many of the files are copied here with a .dist extension for ease of comparison, but none of these files are live and can be deleted if desired. |
| doc, /usr/share/doc/shibboleth-ver | Contains documentation, licenses, and the like. |
| var/log/shibboleth | Contains the shibd.log and transaction.log files by default, though logs can be sent to arbitrary places. |
| var/cache/shibboleth | Contains files created by the software that should survive system restarts, such as backup copies of remote metadata or configuration files and HTTP caching information. Files may be deleted when the software is not in use without preventing future use unless a remote source of configuration is unavailable. |
| var/run/shibboleth | Contains temporary files created by the software that are expected to be transitory and not survive a system restart. Typically PID files, socket files, and the like. |