...
- Installs
log4shib.dllandNTEventLogAppender.dll(and debug) andLOG4CPP.LICENSE NTEventLogAppender.dllhas a version free name;log4shib.dlldoes not.
OpenSAML
t_Note that_ This is a subset of the Shibboleth Merge Module.
- Installs
saml.dll,samlsign.exe,xmltooling.dllandxmltoolinglite.dll(and debug). - Also installs
CREDITS.txt,LICENSE.txt,NOTICE.txt,README.txtandRELEASE.txt - A third (architecture independent) merge module installed the schema files and catalog to
PATH\xml\opensamland {{PATH\xml\xmltooling }}
...
- Installs
libeay32.dll,ssleay32.dll,openssel.exe(and debug) andOPENSSL.LICENSE
Shibboleth
...
- Installs
shibsp.dllandshibsplite.dll(and debug). NOTE that the version is NOT the same as the current shibboleth major version. - A third (architecture independent) merge module installed the schema files and catalog to
PATH\xml\shibboleth
...
- Looks up previous installs (so as to deny incompatible upgrades) using the same mechanism as the old installers
- Looks up (in the 32 bit registry) and, if we are installing the IIS filter, stores (in both registries) the SSO extension
- Sets up the icon for the Add/Remove Programs window
- Looks up any parameters passed to initial install (if there was one). A very few of these are used to allow for seamless upgrade. The rest are there for historic interest.
- Looks to see whether the Shibd_default service is installed. This is used during an upgrade to control whether to restart the service.
- In addition, the IISMAJORVERSION p[roperty (available via the WiX plugin library) is interrogated.
3. Executables
These are all installed in a series of directories under a user chosen directory (default \opt\shibboleth-sp
...
- 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 created are never un-installed.
- Editing IIS. This will be roughly the same as currently but
- The dialog is not offered if IIS is not installed, nor is any other work scheduled.
- Architecture sensitibe sensitive DLLs for the x64 version
- The install the dlls dance 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.
- The Service is only declared if specified by INSTALL_SHIBD_FILTER and this is detected as a first time install (not an upgrade)
- The Service is only removed if this is detected as a last uninstall (not an upgrade)
- 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
- If this is a fresh install call (a modified version of) the current install script
- If this is a final uninstall (detected inside the installer) call the current uninstall script
- Logging
- The VBScript do some minimal logging to
path\var\log\Installer.log
- The VBScript do some minimal logging to
6. The GUI (and not) & command files
The GUI is TBD. Its integrated into the WiX standard GUI so only two dialogs (instal and update) are used. The plumbing was derived from analaysis of the standard GUI based WiX installs.
The new install dialog's 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
If an upgrade is sensed then these values are filled in from a mixture of values stored in the registry (like OLD_INSTALLDIR), whenther the service is installed and so on.
Note that these properties can be passed to the installer in no gui mode:
...
In addition the 32 bit installer detects if it being installed on a 64 bit machine and refuses, instead recommending the 64 bit installer in 32 bit mode.