Before Squash TA Server 1.7.0-RELEASE

Securing your Squash TA server

In order for Squash TM to ask Squash TA Server to execute a job, a user (login / password) with enough rights to execute a job should exist in Squash TA server.

Securing Squash TA server means securing the embedded jenkins. The solution described below (based on jenkins standard security setup) is given for testing purpose only. For an industrialized solution the user should choose the best solution according its environment (More details on securing jenkins)

• • From the jenkins main page, go to "Manage jenkins / Configure System"

  • There check "Enable security" property

  • In "Access Control / Security Realm" select "Jenkins's own user database"

  • Check "Allow users to sign up"

  • For testing purpose on a local computer, the easiest way is to set "Authorization" to "Anyone can do anything"

• • Click "Apply"

Configure TM callback

On Squash TA Server side, the association between the callback URL and the credentials is done in a properties file named conf.properties and located in SQUASH_TA_HOME/execution_home.

In this file, you should define, for each TM Server using this Squash-TA Server, the callback URL and the associated credentials. For a Squash TM Server, which callback URL is http://myServer:8080/squash, and with a taserver / taserver user, you should define the two properties below:

http\://myServer\:8080/squash.login=taserver

http\://myServer\:8080/squash.password=taserver

Note: Be careful, the colons should be escaped in the callback URL.