The Tachyon Server installer detects which Web Server certificate to use by matching the certificate's Subject Alternative Name (DNS) with the HTTPS Host header supplied during installation. As discussed in Design considerations - Tachyon Server Certificates the Subject Alternative Name must include the DNS Alias FQDN of the server of type DNS Name, for example DNS=TACHYON.ACME.LOCAL
To check the HTTPS binding of the Tachyon website use the following steps. These steps can also be used to change the certificate if it has expired, or a new certificate needs to be used.
|
|
|
The Switch will start and then stop if there is an issue with its certificate.
Check the following log files for errors. The default location for Tachyon Server logs is the %AllUsersProfile%\1E\Tachyon folder on the server where Tachyon Server is installed.
For minimum requirements for IIS see Preparation: Windows Server roles and features.
To review the configuration:
The table below shows the IIS web applications used by Tachyon, and the IIS features that affect how users and clients connect. For more detail about these IIS web applications, please refer to Tachyon Architecture: Tachyon Single-Server system.
IIS web application | Stack | Authentication Enabled | SSL Settings | IP Address and Domain Restrictions |
---|---|---|---|---|
Website | Master, Response & DMZ | Anonymous and Windows | Not configured | Not configured |
ActiveEfficiency | Master | Anonymous and Windows | Not configured | Not configured |
Admin | Master | Windows | Not configured | Not configured |
Background | Response & DMZ | Anonymous and Windows Anonymous is used by clients, Windows is used by Consumer API | Require SSL (ignore) | Not configured |
CatalogWeb | Master | Anonymous and Windows | Not configured | Not configured |
Consumer | Master | Windows Basic Authentication is also enabled if using 1E Core 1.0 (for ServiceNow integration) | Require SSL (ignore) | Not configured |
Core | Response & DMZ | Anonymous | Require SSL (ignore) | Local IP addresses (plus remote DMZ Server added manually) |
CoreExternal | Master | Anonymous | Not configured | Not configured |
CoreInternal | Response & DMZ | Anonymous | Not configured | Local IP addresses |
Experience | Master | Windows | Require SSL (ignore) | Not configured |
Platform | Master | Windows | Not configured | Not configured |
Tachyon | Master | Windows | Require SSL (ignore) | Not configured |
The IP Address and Domain Restrictions feature is described in more detail below. Steps for verifying its configuration are provided in Verify IIS Security of the Tachyon Website. |
The Tachyon website uses the IIS feature IP Address and Domain Restrictions to restrict access to Tachyon Server web applications. The following web applications are configured during installation (and upgrade), so that only local connections are allowed, and remote connections are denied.
Other web applications, including Tachyon and Background, are not configured and therefore they allow all local and remote connections.
|
The Tachyon installer uses the PowerShell cmdlet Get-NetIPAddress to list all the IPv4 and IPv6 Addresses and adds them all to the restricted web applications during installation or upgrade. You must modify the configuration of IP Address and Domain Restrictions if the network interface configuration has changed on a Tachyon Server, for example if an IP Address is changed, or a new network interface is installed.
You will also need to modify the configuration of the Response Stack's Core web application to manually add the internal-facing IP Address of a DMZ Server.
If the configuration of any network adapters is changed then the Tachyon website configuration for IP Address and Domain Restrictions may need to be updated with the server's new IPv4 and IPv6 addresses. Failure to update the configuration after a network change will cause issues between the Switch and the Core and prevent the Tachyon Server from functioning.
Use the PowerShell cmdlet Get-NetIPAddress to determine the current IP Addresses, and if necessary update the configuration for the three web applications (Authentication, Core and CoreInternal).
The following AddIpSec.ps1 script can be used to refresh local IP Addresses. It does not remove old, unwanted, or remote IP Addresses.
|
A post-installation verification test is to confirm web browsers do not have remote access to the Core. A remote web browser is not expected to be able to access the Core or CoreInternal web applications, which should return a 'Server Error 403 - Forbidden: Access is denied'. If you are able to access these web applications from a remote computer then it is probable that the IP Address and Domain Restrictions feature is not installed.
Use the following steps to check if the IP Address and Domain Restrictions feature is installed and to install it.
There are a number of reasons why you may see this error when you browse to the Tachyon Portal for the first time. You may also see errors saying Not Authorized or Unauthorized in server log files.
The usual reason for this is the SPN is not registered in AD for the DNS Name used to access the server.
You may see this error when doing post-installation verification tests.
When you use a browser to open an application in the Tachyon Portal, you will see Server Error 403 - Forbidden: 'Access denied' if the internal account used by the Application Pool does not have read access to the Tachyon web application folders. This can happen if Tachyon is installed in a non-default location and the NTFS permissions on the installation folder are not correct. To remedy the issue, you should review and correct NTFS permissions as described in Services and NTFS Security. |
Do not enable Anonymous authentication to fix this type of issue. |
You may see this error when doing post-installation verification tests.
When you use a browser to open an application in the Tachyon Portal, and you see Server Error 404 - 'File not found' the reason is probably because you have not installed the IIS features Web-ASP and/or Web-Asp-Net45. Use the following steps to check if the Web-ASP and/or Web-Asp-Net45 features are installed and to install them.
|