Skip to main content

Viewpoint Vista Authentication

To authorize access to read and write data between your product and Viewpoint Vista using Agave, you or your customer will need to complete the following steps:

Step 1: Whitelist Static IP Addresses

Step 1A: Hosted or Cloud Versions of Viewpoint Vista

If you are using a hosted (cloud) version of Viewpoint Vista, you will need to open a case with Viewpoint Customer Support to add Agave's static IP addresses to your Vista TLS Database Endpoint IP whitelist:

  1. Go to https://support.viewpoint.com/s/

  2. Log in to your Customer Support account.

  3. Select My Resources, then Submit a Case.


  1. Select Support, then Systems/IT.


  1. Under Which product are you using?, input the following and select Search Knowledge Base:
  • Product: select "Vista".
  • Version: select the version of your Vista instance (e.g. 2022 R2).
  • Module: select "Vista Server and IT Related".
  • Brief Summary: input "TLS Database Endpoint IP Whitelist".


  1. Scroll to the bottom of the page and press Continue to Case Creation.

  2. Under Case Create, select a Priority. Under Description, add the following:

Hi - we are looking to whitelist our IPs for TLS Database Endpoint connectivity with our Vista instance. Here are our static IPs:

  1. 13.58.14.240
  2. 18.219.160.98
  3. 3.143.37.24

Could you also let us know what the database name and port are for our instance?

  1. Press Submit.

  2. After submitting a case, you should receive a response from Viewpoint Support within 24-48 hours confirming the connection the IP addresses have been whitelisted. Make a note of the hostname (e.g. {hostname}-sql.viewpointdata.cloud) and port number since you will need to use these to authenticate with Agave Link)

Step 1B: On-premise Versions of Viewpoint Vista

if you are on an on-premise version of Viewpoint Vista, you will need the following three static IP addresses to connect to your SQL server by adding them to your firewall for your network:

  1. 13.58.14.240
  2. 18.219.160.98
  3. 3.143.37.24
note

If you run are unable to authenticate with Agave Link even after adding the above static IP addresses, we recommend following our guide on troubleshooting common issues with on-premise connections.

Step 2: Create a SQL User

After adding Agave to address your Vista TLS Database Endpoint IP whitelist, you will need to create a SQL User to be able to read and write data from and to your Vista Server:

note

If you do not have access to Microsoft SQL Server Management Studio, we recommend following Trimble's guide on creating SQL accounts within Viewpoint Vista.

Some customers also choose to run the Agave Connector on a separate account (rather than admin) on the host machine. Ensure you install the Agave Connector while signed in with the account that will run it.

  1. Open Microsoft SQL Management Studio and log in to your Vista SQL Server.

  2. Select Security, right click Logins, then select New Login....



  1. Under General:
    • Input a new Login name (e.g. "{your product name}-User").
    • Select SQL Server authentication.
    • Add details for a password.
    • Unselect Enforce password policy.
    • Set Default database to be "Viewpoint".


  1. Under User Mapping:
    • In the Database column select "Viewpoint"
    • Select the following under Database role membership for Viewpoint:
      • db_datareader
      • db_datawriter
      • public
      • VCSUsers


  1. Select OK.

You can now authenticate using the SQL user and details about your Vista account using Agave Link. To authenticate, you will need to pass the following components:

  1. Hostname: this is the value for hostname that was provided in response to the case you filed (see step 9 of Open a Case with Viewpoint Support).
  2. Database: this is the name of the database you would like to grant read and write access to (e.g. "Viewpoint").
  3. Port: this is the value for port that was provided in response to the case you filed (see step 9 of Open a Case with Viewpoint Support).
  4. Username and Password: this is the login name and password from when you created a SQL user (see step 2 of Create a SQL User).