KB: Secured port number usage for the Server Email Notifications

Altium On-Prem Enterprise Server Altium On-Prem Enterprise Server
Altium Enterprise Server sends email notifications for various tasks and alerts. However, if these notifications are being sent using the unsecured HTTP port (9780) instead of the HTTPS port, it may pose a security risk. This article summarizes how to configure the server to use the secured HTTPS port for email notifications.

Solution Details

Altium Enterprise Server email notifications are an essential feature for staying informed about updates and changes within your team. However, to ensure that these notifications are delivered with secured port number, it's crucial to configure the server connection settings accurately. In this article, we'll walk you through the process of configuring the Altium Enterprise Server with the Secured email notification and the steps to verify the same. 

Understanding the Importance of Default Port Numbers

The Altium Enterprise Server email notification must use the default port number configured in your LocalVault.ini configuration file for the server connection. If the default port number is the unsecured one, then your email notifications will also follow the same unsecured port. So we must verify the default port number configuration and ensure its IIS bindings for the server connection. 

Step 1: Checking the LocalVault.ini File

To start, we need to check the LocalVault.ini file, which contains the server connection settings. To do this:

1. Navigate to the Server installation folder, typically located at C:\Program Files (x86)\Altium\Altium365.
2. Open the LocalVault.ini file using Notepad or Notepad++ with administrator rights.
3. Update the Website domain with the Secure port number (e.g., 9785 or 443).
4. Ensure the Preferred Protocol is set to "HTTPS".
5. Change the HTTPS port number to 9785 or 443, depending on your requirement.

Example of LocalVault.ini File Configuration

Here's an example of what the LocalVault.ini file configuration might look like:

Example[Server]
WebsiteDomain = yourdomain.com:9785
PreferredProtocol = HTTPS
HTTPSPort = 9785

Step 2: Verifying IIS Bindings

In addition to updating the LocalVault.ini file, we need to ensure that the IIS bindings match the Website domain configuration. To do this:

1. Open the IIS configuration.
2. Check the bindings to ensure they match the Website domain and port number configured in the LocalVault.ini file.

Step 3: Restarting IIS Services and Verifying Email Notification URL

After updating the LocalVault.ini file and verifying the IIS bindings, we need to restart the IIS services to apply the changes. To do this:

1. Restart the IIS services.
2. Recheck the Email notification URL port number to ensure it matches the configured port number.

Troubleshooting Tips

If you encounter issues with email notifications after following these steps, double-check that:

  • The LocalVault.ini file is updated correctly.
  • The IIS bindings match the Website domain configuration.
  • The IIS services are restarted after making changes.

By following these steps and verifying the server connection settings, you should be able to configure your Altium Enterprise Server email notifications to use the secured port as the default port number, ensuring reliable delivery of updates and notifications to your team.

Refer below link for the HTTPS protocol configuration. 

If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.