3.4. Registering with an Activation Key

An on-premise Subscription Asset Manager can pre-configure subscriptions to use for a system, and that pre-configured set of subscriptions is identified by an activation key. That key can then be used to attach those subscriptions on a local system.

3.4.1. Using Activation Keys from the GUI

Activation keys for Subscription Asset Manager are configured before the system is ever created or added to the inventory, and the activation keys are passed as part of registering the system.
  1. Install the configuration RPM or manually configure Red Hat Subscription Manager to point to the subscription application, as in Section 3.3, “Registering with a Subscription Management Application”. For example:
    [root@server ~]# rpm -ivh http://sam.example.com/pub/candlepin-cert-consumer-latest.noarch.rpm
  2. Launch Subscription Manager with the --register option to open the registration screens immediately.
    [root@server ~]# subscription-manager-gui --register
  3. Check the I will use an Activation Key checkbox and click the Next button.
  4. Enter the name of the organization to which the system will belong, the activation key value (an alphanumeric string), and the system name to use for the entry in Subscription Asset Manager.
  5. Click the Register button.
After the registration completes, all of the pre-configured subscriptions are attached to the system.

3.4.2. Using Activation Keys from the Command Line

Activation keys for Subscription Asset Manager are configured before the system is ever created or added to the inventory, and the activation keys are passed as part of registering the system.
  1. Install the configuration RPM or manually configure Red Hat Subscription Manager to point to the subscription application, as in Section 3.3, “Registering with a Subscription Management Application”. For example:
    [root@server ~]# rpm -ivh http://sam.example.com/pub/candlepin-cert-consumer-latest.noarch.rpm
  2. Then, run the register command with the --activationkey parameter to attach the configured subscriptions.
    # subscription-manager register --username=jsmith --password=secret --org="IT Dept" --activationkey=abcd1234
    If there are multiple organizations — or even if there is only a single organization but it is possible for there to be multiple ones — it is still necessary to specify the organization for the system. That information is not defined in the activation key.