Private keys are necessary to configure pools and injectors
To access the Private Keys administration, click on Admin in the navigation bar, and choose Private Keys. A private key corresponds to the ssh key used to connect to your Git repository or pool instances.
To create a Private Key, click on the Create button.
A private key can be scoped on pool or repository. It means that you can only use this private key while configuring a repository or a pool. The all scope can’t be choosen, as it is only there for the legacy private keys without scope.
You have two possibilities to reference private keys:
- Upload them directly by drag-and-drop or click on the input to choose the file on your filesystem
- Locate a private key existing on Gatling Enterprise’s host. The private key permissions should be 600 or 400, and its owner should be the Gatling Enterprise process user
ec2-useruser and then
frontlineuser which is the one running the Gatling Enterprise process.
You can edit the private key by clicking on the icon and delete them using the checkboxes on the table’s right part.