Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
{
   "System": "Tosca",
   "Name": "Tosca Server",
   "Server": "https://<server name>.<domain>.com",
   "Service Account": "<service account name>",
   "Service Password": "<encrypted Password>",
   "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

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.

Record Management Policy Changes

...