Deployment Architecture

Feature Request: register License Slave at License Master with token

Explorer

With scaling infrastructure and the requirement to bind machines to a pool instead of using catch-all (slaves = *) we are looking for a simple and secure way to connect a license slave to the license master.
For now we collect the GUID on the new slave and register it at the License Master with the CLI command. It would be preferable to have something like a 'pool secret/token' that the license slave can use to connect to the license master and register at the pool associated with this token.

Alternative: different CLI command on license slave which asks for LM account with 'license capabilities' to register the local GUID in the correct pool at the LM.

0 Karma