Installation instructions for hot fix E8D001 on Windows for x64

Installation Instructions for Hot Fix E8D001

Windows for x64

Hot fix E8D001 addresses the issue(s) in SAS Web Server 9.45 on Windows for x64 as documented in the Issue(s) Addressed section of the hot fix download page:

http://ftp.sas.com/techsup/download/hotfix/HF2/E8D.html#E8D001

The hot fix downloaded, E8D001pt.zip, contains the updated files required to address the documented issues.
Do NOT extract the contents of E8D001pt.zip. The hot fix installation process will extract the contents as needed.

SPECIAL NOTE REGARDING SECURITY VULNERABILITY

This hot fix requires that your software must already be configured prior to installation. If no configuration directory exists at the time of installation, security updates built into this hot fix will not be completed, leaving your software in a vulnerable state.

IMPORTANT NOTES

Special Note regarding Windows 2008, 2008R, 2012 and 2012R2
If you are running on one of the above mentioned operating systems, you will need to download and install updated VC++ libraries from Microsoft.
Please visit https://www.microsoft.com/en-us/download/details.aspx?id=52685 to obtain these libraries.
Failure to do so will result in SAS Web Server being unable to restart after applying this hot fix.
This updates the version of OpenSSL to 1.0.2r which support FIPS 140-2 compliance.
You must have SAS Web Server 9.45 installed on your system before applying this hot fix. Refer to SN-35968 for instructions on how to determine which product releases you have installed.
Files delivered in this hot fix will be backed up during the installation process. However, it is good general practice to back up your system before applying updates to software.
You must have Administrator Privileges on your CLIENT or SERVER machine.
All currently active SAS sessions, daemons, spawners and servers must be terminated before applying this hot fix.
This hot fix should be installed using the same userid who performed the initial software installation.
CONFIGURATION: No automatic configuration scripting is included for this hot fix. If you have previously configured software installed, the SAS Deployment Manager may present a screen where you will see "Apply SAS Hot Fixes" and "Configure SAS Hot Fixes" options. On this screen, you must ensure that the "Configure SAS Hot Fix" option is *not* selected. If this option is automatically selected, please de-select it prior to proceeding with the SAS Deployment Manager Screens. Failure to do so could have unintended consequences when applying this hot fix.

INSTALLATION

The E8D001 hot fix for SAS Web Server 9.45 will be installed using the SAS Deployment Manager. By default, the SAS Deployment Manager will search in the <SASHOME>\InstallMisc\HotFixes\New directory for hot fixes to be applied, but will also prompt for a location if you have downloaded hot fixes to a different directory.

After downloading E8D001pt.zip, follow the instructions for applying hot fixes in the SAS Deployment Wizard and SAS Deployment Manager 9.4: User's Guide.

Please review the CONFIGURATION Important Note above concerning proper selection of the "Configure SAS Hot Fix" option in the SAS Deployment Manager.

POST-INSTALLATION INSTRUCTIONS

IMPORTANT NOTES Regarding hot fix updates:

For SiteMinder configuration using the updated Apache version, please review information in SASŽ 9.4 Intelligence Platform: Middle-Tier Administration Guide, Fourth Edition
For the updated Apache version delivered in this hot fix, step 2 under "Configuring SAS Web Server for the Web Agent" should read as follows:

Edit the SAS-configuration-directory\Levn\Web\WebServer\conf\httpd.conf file. Add lines that are similar to the following at the beginning of the LoadModule directives:
LoadModule sm_module "C:/Program Files (x86)/CA/webagent/bin/mod_sm24.dll"
SmInitFile "C:/SAS/Config/Lev1/Web/WebServer/conf/WebAgent.conf"
For UNIX deployments, the name of the library is libmod_sm24.so instead of mod_sm24.dll.
If you have configured SSL/TLS manually for SAS Web Server post-deployment, to use SAS Environment Manager to monitor SAS Web Server, complete the following steps:
1. Edit the <SASConfig>/LevX/Web/WebServer/conf/httpd.conf file and make the following changes:
  Replace the line
  Listen 80
  with the following line:
  Listen localhost:7980
  IMPORTANT NOTE: If you use a non-default port, please enter that port number instead of the one listed above
2. Edit the <SASConfig>/LevX/Web/WebServer/conf/extra/httpd-ssl.conf file and make the following changes:
  Locate the following lines for the certificate file and key file and enter the correct filenames: SSLCertificateFile "ssl/myhost.crt"
  SSLCertificateKeyFile "ssl/myhost.key"
  SSLCertificateChainFile "ssl/myhost.crt
If you manually configured SSL/TLS for SAS Web Application Server, complete the following step
1. Edit the <SASConfig>/LevX/Web/WebServer/conf/sas.conf file and add the following two lines:
  SSLProxyCheckPeerCN off
  SSLProxyCheckPeerName off
If you configured SSL/TLS for SAS Web Server and SAS Environment Manager is not configured for SSL/TLS and is also on the same machine as the Web Server, then complete this step if applicable:
1. Edit the <SASConfig>/LevX/Web/WebServer/conf/sas.conf file and comment out the following directive:
  Replace the line
  Header set Strict-Transport-Security "max-age=31536000"
  with the following line:
  #Header set Strict-Transport-Security "max-age=31536000"
(Optional) When FIPS mode is enabled in the SAS Mid-Tier environment the system will enforce an order of precedence by negotiating cipher suites with perfect forward secrecy (PFS) and then cipher suites without it for compatibility with legacy applications. If PFS needs to be strictly enforced then the SAS Web Application Server config file can be updated with the following changes.
Edit each SAS Web Application Server's <SASConfig>/LevX/Web/WebAppServer/SASServerX_X/conf/server.xml file and make the following changes:

Replace the ciphers attribute in Connector element:
ciphers="TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA"
with the following line:
ciphers="TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"