Description of problem: When attempting to use activation keys I get a generic authentication error as seen below: subscription-manager register --activationkey xxxxxxxxxxx --org "xxxxxxx" Invalid username or password. To create a login, please visit https://www.redhat.com/wapps/ugc/register.html Version-Release number of selected component (if applicable): subscription-manager: 1.1.23-1.el6 python-rhsm: 1.1.8-1.el6 How reproducible: Happens every time Steps to Reproduce: 1. Run subscription-manager as described above with valid activationkey and org 2. Get error message listed above Actual results: System is unregistered Expected results: No error message, system registered Additional info: We are using the Customer Portal, not our own SAM installation Excerpt from man page: --activationkey=KEYS Gives a comma-separated list of product keys to use to redeem or apply specific subscriptions to the system. This is used generally for preconfigured systems, which may already have products installed and subscriptions attached to that system. When the --activationkey option is used, it is not necessary to use the --username and --pass- word options, because the authentication information is implicit in the activation key. When there is a single organization or when using the Customer Portal Subscription Management service, it is not necessary to specify an organization with the --org option, but in multi- organization environments, this is required. For example: subscription-manager register --org="IT Dept" --activationkey=1234abcd Giving the org name is not necessary when there is a single organization or when using the Cus- tomer Portal Subscription Management service.
Activation keys are not supported by the custoemr portal.
The man page seems to indicate that they are. Under the activationkeys section of the man page: "Giving the org name is not necessary when there is a single organization or when using the Customer Portal Subscription Management service." If they are unsupported, this statement is irrelevant. Also the example doesn't show the use of serverurl: "subscription-manager register --org="IT Dept" --activationkey=1234abcd" Is there documentation to say that it is unsupported?
ok.. I will make this a doco request.
Do activation keys server another purpose? I have the ability to make them in the Red Hat Customer Portal: http://joeceresini.com/dump/uploads/rhel-activation-keys.png
The customer portal is combining RHN Classic functionality (which has activation keys) with subsciption management which does not.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Version: Brew Build # subscription-manager version server type: Red Hat Subscription Management subscription management server: 0.8.7-1 subscription-manager: 1.8.8-1.el5 python-rhsm: 1.8.11-1.el5_9 Verification: --activationkey=KEYS Gives a comma-separated list of product keys to use to redeem or apply specific subscriptions to the system. This is used for preconfigured systems, which may already have products installed and subscriptions attached to that system. Activation keys are issued by an on-premise subscription management service, such as Subscription Asset Manager. When the --activationkey option is used, it is not necessary to use the --username and --password options, because the authentication information is implicit in the activation key. For example: subscription-manager register --org="IT Dept" --activationkey=1234abcd The above is updated man page for "subscription-manager" -> "register options" -> "--activation-key" It no longer mentions "Customer Portal Subscription Management" VERIFIED
Refer bug description (https://bugzilla.redhat.com/show_bug.cgi?id=956285#c0) for previous man page on --activation-key.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1332.html