The patch files for the SPAS system are packaged in a zip archive. Within this archive, you will find a root folder labeled "Server Update."
This folder contains several sub-folders, each corresponding to a specific product component included in the patch as shown below:
The potential sub-folders in the patch are as follows:
**MfaServer**: Contains the MFA server along with the SurePassID portal.
**ApiServer**: Houses the API server that manages most of the mobile and WebAuthn product functionalities.
**Saml2Idp**: Contains the SAML 2 Identity Provider (IdP).
**ServicePass**: Comprises the SurePassID self-service portal.
The names of these sub-folders match the structure of the SurePassID installation folder, which is found at "C:\Program Files (x86)\SurePassID Corp\SurePassID Authentication Server <release>." For instance, this structure is exemplified in the case of Release 24.2.
Please be aware that the following steps may require a brief period of downtime, so it is advisable to plan accordingly.
Step 1: Begin by extracting the contents of the patch (downloaded zip) file into a designated folder for easy access.
Step 2: Next, access the IIS Manager and stop the SurePassID sites. If the IIS is exclusively serving the SPAS system, you can opt to stop the entire IIS service.
Step 3: It is crucial to create a backup of the main SurePassID installation folder to safeguard against any potential issues.
Step 4: Proceed to replace the existing folders in the SurePassID installation folder main directory with the corresponding folders from the extracted patch. Ensure that you overwrite the current files with the updated patch files. For example, if you are applying a patch that has the MfaServer and Api Server folders you could copy each of those folder (or both) into the SurePassID installation folder. "C:\Program Files (x86)\SurePassID Corp\SurePassID Authentication Server <release> relacing the existing files.
Step 5: Once the files have been successfully replaced, restart the IIS services and/or the individual sites.
Step 6: Log into the SPAS portal and verify the build number displayed at the bottom of the page. The date of the patch should correspond with the date shown in the build section.
Step 7: Finally, conduct sign-in tests for the relevant systems to confirm that our authentication system is functioning properly.