Bug 860030 - server version check should not use consumer authentication
Summary: server version check should not use consumer authentication
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: subscription-manager
Version: 5.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Adrian Likins
QA Contact: Entitlement Bugs
URL:
Whiteboard:
Depends On:
Blocks: 771748
TreeView+ depends on / blocked
 
Reported: 2012-09-24 16:46 UTC by Adrian Likins
Modified: 2013-01-08 04:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-08 04:03:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0033 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2013-01-08 08:38:27 UTC

Description Adrian Likins 2012-09-24 16:46:20 UTC
Description of problem:

server versions checks in managercli use the default candlepin UepConnection
object, which is a consumer authenticated connection.

This is not necessary for server version check (just needs get /, and
get /status, which do not require auth). 

One of the consequences of this is that attempting to do this for
a consumer that has been deleted causes a 410 ("GoneException"). This
is caught and logged and handled, but it doesn't need to happen.



Steps to Reproduce:
1.

subscription-manager version

(or any subscription-manager commands that make a connection, list --available for example)
  
Actual results:

Note in the log that the GET / connection uses certificate auth, this is unneed

Expected results:

that connection should use no auth, log should indicate "using no auth"


Additional info:

Comment 1 Adrian Likins 2012-09-26 17:40:27 UTC
commit 2ecf9e4552f25a2ebb361f8d5166b2ff07b16cf1
Author: Adrian Likins <alikins>
Date:   Mon Sep 24 12:35:55 2012 -0400

    860030: make server_version_check use a non authenticated call

Comment 2 RHEL Program Management 2012-10-01 21:08:27 UTC
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.

Comment 4 spandey 2012-10-08 11:23:06 UTC
Verified using following rpm 

subscription-manager-migration-1.0.21-1.el5
subscription-manager-1.0.21-1.el5
subscription-manager-migration-data-1.11.2.6-1.el5
subscription-manager-gui-1.0.21-1.el5
subscription-manager-firstboot-1.0.21-1.el5

log output with version command 

2012-10-08 16:50:15,488 [DEBUG]  @profile.py:95 - Loading current RPM profile.
2012-10-08 16:50:15,616 [INFO]  @managercli.py:252 - Client Versions: {'python-rhsm': '1.0.9-1.el5', 'subscription-manager': '1.0.21-1.el5'} 
2012-10-08 16:50:15,617 [INFO]  @connection.py:498 - Using certificate authentication: key = /etc/pki/consumer/key.pem, cert = /etc/pki/consumer/cert.pem, ca = /etc/rhsm/ca/, insecure = False
2012-10-08 16:50:15,617 [INFO]  @connection.py:511 - Connection Built: host: 10.65.193.112, port: 8443, handler: /candlepin
2012-10-08 16:50:15,618 [INFO]  @connection.py:508 - Using no auth
2012-10-08 16:50:15,618 [INFO]  @connection.py:511 - Connection Built: host: 10.65.193.112, port: 8443, handler: /candlepin
2012-10-08 16:50:15,619 [DEBUG]  @connection.py:323 - Loading CA PEM certificates from: /etc/rhsm/ca/

working fine resolving defect as verified

Comment 6 errata-xmlrpc 2013-01-08 04:03:32 UTC
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-0033.html


Note You need to log in before you can comment on or make changes to this bug.