...
- Editing the config files.
- The same process as currently (note that some of the editing will be moved to the merge modules in order to get the catalogs located correctly)
- This process will be run on installs and on upgrades, but the edit code is sensitive to not overwriting these files. Thus files can be via this mechanism on upgrades.
- The files create are never un-installed.
- Editing IIS. This will be roughly the same as currently but
- Architecture sensitibe DLLs for the x64 version
- The install will only be called if we know this is a from fresh install
- The uninstall will only be called if we know this is a not an upgrade
- Edit the Service (x64 only)
- The service is declared (because it has to be done there) with the 32 bit install of shibd.
- IFF we are doing the first install and the user has specified x64, then the path to shibd is changed to point at the x64 prior to the service being started.
- Environment Variables
- Add the lib direcrtory(s) that the merge modules installed into into the path
- Add (currently via javascript) SHIBSP_PREFIX to point to the shib install dir
6. The GUI
...
(and not) & command files
The GUI is TBD. Its job is to set the following properties which are then passed to the installer.
- INSTALLDIR (default {c:\opt\shibboleth-sp}} - where to install Shibboleth
- SHIB_FILE_EXTENSION (default ".sso") - the extension to register (for IIS)
- INSTALL_ISAPI_FILTER (default "TRUE") - whether to register with IIS
- INSTALL_SHIBD_SERVICE (default "TRUE") - whether to register the service
- INSTALL_32BIT (tbd) - whether to register 32 or 64 bit service (and IIS plugins)
- SHIBD_PORT" (default "1600") - the port that shibd will listen on
Note that these properties can be passed to the installer in no gui mode:
Code Block |
---|
msiexec /qn /i ShibboltherSP-x64.msi INSTALLDIR=d:\Path\MorePath SHIBD_PORT
|
Command files shipped with the installer include:
keygen
As currently, this generates the LLSS certificate key pair.
SetService64 (x64 install only)
This stops the shibd, sets the path such that from now on the 64 bit version of shibd is run and then restarts shibs
SetService32 (x64 install only)
This stops the shibd, sets the path such that from now on the 32 bit service of shibd is run and then restarts shibs
7. Versioning
All version information (and some other global configuration) is contained in the header file Versions.wxi
It is an assumption that all DLLs have versioning information encoded in the name such that a change of API will cause the DLL name to change. If the DLL name changes then it is vital that the associated component GUID change as well.
...