Forum Discussion

lambdaburst's avatar
lambdaburst
New Contributor
2 months ago
Solved

On-premises Azure build agents running TestExecute with ID-based licensing

We recently migrated our self-hosted Azure DevOps Build agents from HASP based licensing to the ID based licensing.  We use a test adapter via the COM integration to execute and pull test data back i...
integrations
  • lambdaburst's avatar
    lambdaburst
    2 months ago

    Opened a support ticket and Support was able to tell me about an undocumented method of generating an Access Key for anonymous.user and manually substituting this in the local auth files for TestComplete/TestExecute.

    I'm not sure they want the details in the public so if you encounter the same hang up, just contact them.

rraghvani's avatar
rraghvani
Icon for Champion Level 3 rankChampion Level 3
2 months ago

Are you referring to?

/AccessKey:access_key

This parameter is for those who use SmartBear ID-based licenses of TestComplete. It specifies the access key associated with your SmartBear account and is used to license the product in automated runs that don’t require user interaction. For more information on this and on how to get the key, see Activate TestComplete in CI/CD build runs.

lambdaburst's avatar
lambdaburst
New Contributor
2 months ago

Yes but no.  An ID-based access key is required for this situation, but as I alluded to initially, when using the COM integration you aren't launching TestComplete/TestExecute via command line and cannot specify the AccessKey parameter.

There is a way to generate an AccessKey for the On-Premises License Server using anonymous.user, and then substitute that key for the normal ID-based token.

Since that is not documented publicly, I won't elaborate on it here, but those that need it can discuss the process with the support team.