Deployment Architecture

Feature Request: register License Slave at License Master with token

ischoenmaker
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
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...