Tricentis Vera Cloud pre-deployment checklist

• 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.

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.

• 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).

Have the following ready before you register your IdP in Vera:

• IdP Entity ID.

• Single sign-on (login) URL.

• Single logout URL, if your IdP supports it.

• Signatures Entity ID and Signatures URL, if your IdP uses a separate endpoint for e-signatures.

• One or more PEM-encoded X.509 public certificates (.pem, .crt, or .cer).

• Authentication context class references your IdP expects.

On the Service Provider page in Vera, note the Login Entity Id and Signatures Entity Id. Configure those Entity IDs in your SAML IdP so it recognizes Vera. The IdP endpoint for the 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 for signatures.

Before you enable SSO, set at least one Site Administrator account to use Vera (local) authentication. This keeps you signed in if SAML stops working.

• 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.