Welcome to

Tricentis Vera Cloud!

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

URLs and Ports 

•  

  Open Outgoing TCP Port Access from your Environment to

  VERA

  Vera Cloud

  •  

    443

  •  

    8443

Your environment will need to communicate with both the VERA Vera Web Portal on port 443 and the VERA Vera API Server on port 8443. VERA 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 Tx3 Tricentis Account Manager and different ports can be provisioned. This may need to be repeated on each server that will connect to VERAVera.

•  

  Allow Outgoing Access to the

  VERA

  Vera Cloud URL

If your environment restricts access to an approved list of URLs, you will need to add the VERA Vera Cloud URL to that list. Typically the url will follow this pattern: https://[your-company-name]-vera.saas.tx3servicestx3helios.com. Your specific URL will be communicated to you by your Tx3 Tricentis Account Manager. This may need to be repeated on each server that will connect to VERAVera.

•  

  Allow Incoming Access from

  VERA

  Vera Cloud to your Environment

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 Vera Cloud URL and using your endpoint's API port. This may need to be repeated on each server that VERA Vera will connect to.

•  

  Provide

  Tx3

  Tricentis with your Endpoint URL and API Port Information

You must provide Tx3 Tricentis with your endpoint's API port and URL information. VERA 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 Vera will connect to.

Service Accounts

•  

  Create a Service Account in your Endpoint System

You must create a Service Account for VERA 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 VERAVera. This will need to be repeated on all endpoints.

•  

  Provide the Service Account Credentials to

  Tx3

  Tricentis

The credentials will be stored in VERA Vera in order to access your endpoint system. The password will be encrypted before storing it in VERAVera. 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

•  

  Provide

  Tx3

  Tricentis with a List of User Accounts

  •  

    VERA

    Vera Service Account

  •  

    Local Admin Accounts

  •  

    Local User Accounts

  •  

    SAML User Accounts

JIRA endpoints will need to communicate with VERA Vera using a VERA 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 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 Vera Cloud environment is configured (see Import VERA Vera users for more information on the CSV Import process).

SAML Setup

•  

  Provide

  Tx3

  Tricentis with SAML 2.0 Identity Provider Details

  •  

    URL

  •  

    Certificate

•  

  Add

  VERA

  Vera Cloud Service Provider Entity IDs to your SAML IdP

  •  

    Tx3VERA

    Tricentis Vera

  •  

    Tx3VERASignatures

    Tricentis Vera Signatures

Policies

•  

  Provide

  Tx3

  Tricentis with Existing Policy Files

  •  

    Approval Policy

  •  

    Records Management Policy

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