Bug 1096058 - registering a client with invalid password doesn't raise any error on stdout
Summary: registering a client with invalid password doesn't raise any error on stdout
Keywords:
Status: CLOSED DUPLICATE of bug 1094142
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Subscription Management
Version: 6.0.3
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Katello Bug Bin
QA Contact: Sachin Ghai
URL:
Whiteboard:
: 1096803 1100011 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-09 07:47 UTC by Sachin Ghai
Modified: 2014-06-19 19:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-27 15:45:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sachin Ghai 2014-05-09 07:47:51 UTC
Description of problem:
I was registering a client via subscription-manager against sat6 server, and entered a wrong password as below:

[root@scroponok yum.repos.d]# subscription-manager register --username admin --password admin
[root@scroponok yum.repos.d]# subscription-manager register --username admin --password 123
[root@scroponok yum.repos.d]# 

I didn't get any error on stdout, so it doesn't confirm if the command was successful or failed.

/var/log/rhsm/rhsm.log says:
======================
Traceback (most recent call last):
  File "/usr/share/rhsm/subscription_manager/managercli.py", line 1045, in _do_command
    owner_key = self._determine_owner_key(admin_cp)
  File "/usr/share/rhsm/subscription_manager/managercli.py", line 1148, in _determine_owner_key
    owners = cp.getOwnerList(self.username)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 852, in getOwnerList
    return self.conn.request_get(method)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 541, in request_get
    return self._request("GET", method)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 469, in _request
    self.validateResponse(result, request_type, handler)
  File "/usr/lib64/python2.6/site-packages/rhsm/connection.py", line 511, in validateResponse
    raise RestlibException(response['status'], error_msg)
RestlibException



production.log on server says:
============================

Processing by Katello::Api::V1::RootController#resource_list as JSON
  Parameters: {"api_version"=>"v1", "root"=>{}}
Completed 200 OK in 25ms (Views: 3.5ms | ActiveRecord: 0.0ms)
Processing by Katello::Api::V1::PingController#server_status as JSON
  Parameters: {"api_version"=>"v1", "ping"=>{}}
Completed 200 OK in 1ms (Views: 0.2ms | ActiveRecord: 0.0ms)
Processing by Katello::Api::V1::CandlepinProxiesController#list_owners as JSON
  Parameters: {"api_version"=>"v1", "login"=>"admin", "candlepin_proxy"=>{}}
invalid user
[ WARN 2014-05-09 07:29:13 cp_proxy  #11291] SSO failed
  Rendered api/v1/errors/unauthorized.json.rabl (0.4ms)
Filter chain halted as :authorize rendered or redirected
Completed 401 Unauthorized in 189ms (Views: 1.4ms | ActiveRecord: 0.8ms)


Version-Release number of selected component (if applicable):
Satellite 6 Beta Snap 4

Satellite-6.0.3-RHEL-6-20140508.1

on client:
==========
subscription-manager-1.9.11-1.el6.x86_64
katello-agent-1.5.3-1.el6sat.noarch

onserver:
* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.7-1.el6_5.noarch
* candlepin-scl-1-5.el6_4.noarch
* candlepin-scl-quartz-2.1.5-5.el6_4.noarch
* candlepin-scl-rhino-1.7R3-1.el6_4.noarch
* candlepin-scl-runtime-1-5.el6_4.noarch
* candlepin-selinux-0.9.7-1.el6_5.noarch
* candlepin-tomcat6-0.9.7-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.6.0.7-1.el6sat.noarch
* foreman-compute-1.6.0.7-1.el6sat.noarch
* foreman-gce-1.6.0.7-1.el6sat.noarch
* foreman-libvirt-1.6.0.7-1.el6sat.noarch
* foreman-ovirt-1.6.0.7-1.el6sat.noarch
* foreman-postgresql-1.6.0.7-1.el6sat.noarch
* foreman-proxy-1.6.0.4-1.el6sat.noarch
* foreman-release-1.6.0-0.develop.201405061106gitfdc476d.el6.noarch
* foreman-selinux-1.5.0-0.develop.el6sat.noarch
* foreman-vmware-1.6.0.7-1.el6sat.noarch
* katello-1.5.0-22.el6sat.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.5-1.el6sat.noarch
* katello-installer-0.0.37-1.el6sat.noarch
* openldap-2.4.23-32.el6_4.1.x86_64
* pulp-katello-plugins-0.2-1.el6sat.noarch
* pulp-nodes-common-2.3.1-0.4.beta.el6sat.noarch
* pulp-nodes-parent-2.3.1-0.4.beta.el6sat.noarch
* pulp-puppet-plugins-2.3.1-0.4.beta.el6sat.noarch
* pulp-rpm-plugins-2.3.1-0.4.beta.el6sat.noarch
* pulp-selinux-2.3.1-0.4.beta.el6sat.noarch
* pulp-server-2.3.1-0.4.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.0.8-1.el6sat.noarch
* rubygem-hammer_cli-0.1.0-12.el6sat.noarch
* rubygem-hammer_cli_foreman-0.1.0-12.el6sat.noarch
* rubygem-hammer_cli_foreman_tasks-0.0.2-5.el6sat.noarch
* rubygem-hammer_cli_katello-0.0.3-22.el6sat.noarch


How reproducible:
always

Steps to Reproduce:
1. install following package on client.. pull it from server
katello-ca-consumer-dhcp201-122.englab.pnq.redhat.com-1.0-1.noarch
2. install katello agent
3. register client with subscription-manager

Actual results:
registering a client with invalid pasword doesn't raise any error on stdout.

Expected results:
User should get proper error message.

Additional info:

Comment 1 RHEL Program Management 2014-05-09 07:55:13 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Sachin Ghai 2014-05-13 05:19:57 UTC
*** Bug 1096803 has been marked as a duplicate of this bug. ***

Comment 5 sthirugn@redhat.com 2014-05-22 18:48:08 UTC
FWIW this is what happens in SAM when testing a same scenario against SAM server.

# subscription-manager register --org="rhelclienttest" --force --autosubscribe
Username: admin
Password: <Incorrect password>
Invalid credentials

Comment 6 sthirugn@redhat.com 2014-05-22 18:49:15 UTC
*** Bug 1100011 has been marked as a duplicate of this bug. ***

Comment 7 Brad Buckingham 2014-05-27 15:45:46 UTC

*** This bug has been marked as a duplicate of bug 1094142 ***


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