Synchronization Policy Changes
The Synchronization policy must be updated to reflect connection information for qTest and Tosca.
...
| Code Block |
|---|
{
"System": "Tosca",
"Name": "Tosca Server",
"Server": "https://<server name>.<domain>.com",
"Service Account": "<service<client account name>id>",
"Service Password": "<encrypted client Password>secret>",
"Urls": {
"Browser": "https://<server address>/rest/toscacommander/",
"API": "https://<server address>/rest/toscacommander/"
},
"Auth Mode": "clientCredentials"
} |
| Note |
|---|
Using HTTPS? If you are using HTTPS for the Tosca server, then you are required to provide a Client ID and Client Secret for the Tosca Synchronization user and to set the Auth Mode to “clientCredentials”. This user must be a member for the Locking Group for qTest entities in Tosca. The Group must also be created using the User Administration service available in the Tosca Gateway. NOTE: The service account must be created with Tosca Server User Administration and the project needs to be configured for server login. The service account should be added to the Locking Group (example: ALM_Lock) |
| Note |
|---|
Using HTTP? If you are using HTTP for the Tosca Server, then you can provide either a username and password or a client id and secret. Only set the Auth Mode property above to “clientCredentials” when using a client id and secret. The user must be a part of the Locking Group being used to qTest. NOTE: The service account must be created in Tosca Commander Project and added to Locking Group (example. ALM_Lock) |
Record Management Policy Changes
The Records Management policy should be updated to reflect the desired fields that will be displayed in VERA. At minimum, it should contain definitions for the following:
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Click on this link to download a sample file. |