Tricentis Vera Cloud pre-deployment checklist

As you prepare to utilize Vera's centralized electronic approval repository, you can use the checklist below to guide you on your way.

Note: Tricentis Vera is capable of connecting to an unlimited number of endpoints and, as such, some of the steps below can be repeated to connect your Tricentis Vera Cloud environment to as many endpoints as your need.

URLs and ports

  • 443

  • 8443

Your environment will need to communicate with both the Tricentis Vera Web Portal on port 443 and the Vera API Server on port 8443. Vera uses SSL communication for all incoming requests and requires ports that are different than the standard (non-SSL) web communication ports. If you cannot use 443 or 8443, please notify your Tricentis Account Manager and different ports can be provisioned. This may need to be repeated on each server that will connect to Vera.

If your environment restricts access to an approved list of URLs, you will need to add the Vera Cloud URL to that list. Typically the URL will follow this pattern:

https://[your-company-name]-vera.saas.tx3helios.com

Your specific URL will be communicated to you by your Tricentis Account Manager. This may need to be repeated on each server that will connect to Vera.

Vera will need to communicate back to your endpoint server and utilize your endpoint's API. The incoming traffic must be allowed from the Vera Cloud URL and using your endpoint's API port. This may need to be repeated on each server that Vera will connect to.

You must provide Tricentis with your endpoint's API port and URL information. Vera will use this information to communicate back to your endpoint as records are approved or rejected. This may need to be repeated on each server that Vera will connect to.

Service accounts

You must create a service account for Vera to access your endpoint. The service account should have sufficient privileges to update records via API in all projects that will be connected to Vera. This will need to be repeated on all endpoints.

The credentials will be stored in Vera in order to access your endpoint system. The password will be encrypted before storing it in Vera. A screen share session can be setup if you wish to encrypt and enter the password  yourself. This will need to be repeated for all endpoints.

Local users

  • Vera Service Account

  • Local Admin Accounts

  • Local User Accounts

  • SAML User Accounts

Jira endpoints will need to communicate with Vera using a Vera Service Account. This account will be created when your cloud environment is configured. You should provide the Service Account Name and expected password. This same account will be stored in the Vera for Jira Add-On configuration settings. Additional user accounts can be supplied at this time as well. Please provide a .csv file to import when your Vera Cloud environment is configured (see Import Vera users for more information on the .csv import process).

SAML setup

  • URL

  • Certificate

If you are using a SAML 2.0 SSO engine, please provide the Single Sign-On service URL for your IdP and the public certificate associated with that IdP.

Tricentis Vera

Tricentis Vera Signatures

On your SAML IdP, please configure the above entity IDs that Vera will use to communicate with your IdP. The IdP endpoint for the Tricentis Vera Signatures entity ID must accept either the ForceAuthN parameter or the "urn:oasis:names:tc:SAML:1.0:am:password" Authentication Context to force re-authentication.

Policies

  • Approval Policy

  • Records Management Policy

If you have existing Vera Policy Files, please send these to Tricentis so that they can be included in your Tricentis Vera Cloud Environment. These policy files may be different for each endpoint.