Important Update: Changes to Board Cloud Security and Connection Settings
What’s changing?
At Board, we prioritize safeguarding your data, information, and other assets managed through our platform. To ensure robust protection, we continuously enhance our cloud security policies.
Starting June 30, 2023, we will close the port range 9700-9710 for incoming TCP connections. This change supports new architectural models that will significantly bolster the overall security of your Board cloud environment.
What does this mean for you?
After June 30, 2023, inbound TCP connections on ports 9700-9710 from the Board Office Add-in will no longer be permitted.Moreover, locally installed Procedure launchers utilizing TCP connections on ports 9700-9710 to initiate Procedures on Board Cloud Platforms will cease to function: if you need to perform tasks like these on a Board Cloud Platform from external systems, we recommend using Board REST APIs.
Next steps
If your Board users connect to your Board Platforms via the Board Office Add-in using the TCP protocol, they should switch their connection protocol to HTTPS in the Office Add-in connection settings.
To make this change, please follow these steps:
1. Open the Microsoft Office application where the Board Office Add-in is installed.
2. Navigate to the “Board” tab and click on the “Connect” icon to bring up the connection dialog.
3. Click “Edit” to access the host management dialog and locate the host name using the TCP protocol with an associated port in the range of 9700-9710.
4. Enter a valid host name that uses the HTTPS protocol.
5. Click “OK” to save the new settings.
6. Clear Browser cache settings.
Upon logging in with the new host, your users will be prompted to enter their Board login credentials in a new browser window. Once they have entered their credentials, the browser window will automatically close, and they will regain access to all Board Office Add-in features as they did before.
If you prefer to change the configuration for all users in a single operation, you can do so using the Windows Group Policy. Simply follow these steps:
- Locate the file named "client_config.xml" in the following directory on a properly configured workstation: [user]\AppData\Roaming\Board International\Board 7.0\
- Copy the "client_config.xml" file from the configured workstation.
- Ensure that the source file being copied contains only one connection that points to the new HTTPS endpoint.
Once you have copied the file, you can distribute it to all users using the Windows Group Policy.
We’re here to help
If you have any questions about this upcoming change, please don’t hesitate to reach out to your Customer Success Manager, your Key Account Manager or contact us at any time.