Workbench Server / SQL Databases in Different Domains
Pragmatic Works Software does NOT provide support nor do we suggest this scenario
Almost all of the modifications require altering operating system, Internet Information Services, and domain settings. Proceed with caution and always make a backup before modifying anything.
The methods described below are for advanced IT administrators who are comfortable with and have been allowed to alter any required settings and/or security protocols. These helpful hints are only for illustrative purposes and each environment will have its own unique requirements and hurdles.
Hosting Workbench Server on a computer that's in a different Microsoft Windows domain than the databases needed to store information can be accomplished by using Windows Authentication or SQL Authentication. Accessing machines across domains carries additional security risks that need to be taken into consideration before implementing this scenario.
Using Windows Authentication to access cross-domain databases
1. Ensure that there's a domain trust between the two domains. The following Microsoft TechNet article explains: https://technet.microsoft.com/en-us/library/cc961481.aspx
2. Open and secure any necessary ports for communication between Workbench Server and any SQL Server instance. Port 1433 is the most common port assigned to SQL Server.
3. While installing Workbench Server:
o The domain user used in the next two steps must belong to the domain that has trust. The relationship defined within the Domain Controllers Domain Trusts area will dictate which domain the user must be defined within.
o Ensure that the user installing Workbench Server has access to the other domain's database servers so that the installation SQL scripts can execute and create databases, tables, etc.
o Specify a user for the various application pools which has access to the other domain's database servers. This domain user will be used to run the website and will need to create, update, and delete database objects in the same manner as a single-domain installation.
4. If the domain user installing Workbench doesn't have the appropriate rights on the other domain, installation may fail.
Using SQL Authentication to access cross-domain databases
1. Open and secure any necessary ports for communication between Workbench Server and any SQL Server instance. Port 1433 is the most common port assigned to SQL Server.
2. While installing Workbench Server, specify the SQL Server instance and database as usual although a static IP address will most likely be used instead of a friendly name.
3. Be sure to include the user name and password as usual.