Workers, Fleets and Certificates
Create a new Fleet
Create a new Fleet in an organization you’re currently logged in to.
List workers which are part of your Fleet
Add a new Worker to your Fleet
Each Worker must reside in a specific Fleet.
Update the properties of your Worker
View Worker client certificates
Worker authenticates with the API by means of a client certificate initially provided to it as part of the registration process.
Issue a new Worker certificate
New worker certificate can be issued at any given time. If an existing client certificate is soon to be expired or has been revoked for any reason, a newly issued certificate can then be placed on the worker for it to be used instead of the current one.
Revoke an existing certificate
In case an existing certificate has been compromised, a new one should be issued and replaced, followed by revocation of the compromised certificate. You will require a certificate’s unique SHA-256 fingerprint in order to identify it at API level. If you have the certificate file, you can retrieve the fingerprint using the following command:
Once a certificate is revoked, it can no longer be used for worker authentication.