RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1265394 - Unauthorized: Invalid credentials for request
Summary: Unauthorized: Invalid credentials for request
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-rhsm
Version: 7.1
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: candlepin-bugs
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-09-22 19:46 UTC by agilley
Modified: 2015-09-24 22:41 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-24 22:41:38 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
rhsm.log (165.18 KB, text/plain)
2015-09-22 19:46 UTC, agilley 		no flags Details
View All

Description agilley 2015-09-22 19:46:41 UTC 
Created attachment 1075983 [details]
rhsm.log

Description of problem: Appears to be a reappearance of bug # 998033 

https://bugzilla.redhat.com/show_bug.cgi?id=998033

When trying to register a rhel 7.1 system a message returns with the error "Unauthorized: Invalid credentials for request"


Version-Release number of selected component (if applicable): RHEL 7.1


How reproducible: continuous 


Steps to Reproduce:
1. subscription-manager register 
2. subscription-manager register --username _______ --password _______
3. subscription-manager register --username _______ --password _______ --auto-attach

Actual results: Unauthorized: Invalid credentials for request


Expected results: Successful registration 


Additional info: /var/log/rhsm/rhsm.log is attached.
Comment 3 John Sefler 2015-09-23 12:48:34 UTC 
The top of your rhsm.log shows...
2015-09-20 03:26:04,121 [DEBUG] rhsmd @identity.py:131 - Loading consumer info from identity certificates.
2015-09-20 03:26:04,121 [DEBUG] rhsmd @identity.py:143 - Reload of consumer identity cert /etc/pki/consumer/cert.pem raised an exception with msg: [Errno 2] No such file or directory: '/etc/pki/consumer/key.pem'

A successful registration using subscription-manager will land two files...
/etc/pki/consumer/cert.pem
/etc/pki/consumer/key.pem

You appear to be missing the key.

I'll bet you registered a consumer using the customer portal web app and then downloaded the consumer cert and then copied it into /etc/pki/consumer/cert.pem.  I'll bet the key actually appended to the end of cert.pem.

On the other hand, I see this in the logs...
2015-09-21 08:45:32,291 [DEBUG] subscription-manager @connection.py:420 - Loaded CA certificates from /etc/rhsm/ca/: candlepin-stage.pem, redhat-uep.pem, katello-server-ca.pem

which indicates to me that you are probably registering to a katello server.  Maybe your katello server was re-deployed and now you have a bad ca cert and stale consumer.

Bottom line... you are missing etc/pki/consumer/key.pem
Comment 4 agilley 2015-09-24 22:41:38 UTC 
I completely missed that. Sorry for the bug report.
Note You need to log in before you can comment on or make changes to this bug.