Bug 712072

Summary: Unexpected message from ipa-getcert with non-root user
Product: Red Hat Enterprise Linux 5 Reporter: Kaleem <ksiddiqu>
Component: certmongerAssignee: Nalin Dahyabhai <nalin>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.7CC: dpal, jgalipea, kchamart
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: certmonger-0.50-1.el5 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-21 06:17:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Kaleem 2011-06-09 12:37:44 UTC 
Description of problem:
Unexpected message from ipa-getcert when called by non-root user.

Version-Release number of selected component (if applicable):
certmonger-0.42-1.el5

How reproducible:
Always

Steps to Reproduce:
1.Install certmonger
2.Start certmonger service
3.run 'ipa-getcet list' command as non-root user.
  
Actual results:
Following message is displayed on console.
"Number of certificates and requests being tracked: 0." 

Expected results:
Following error message should be displayed.
"Insufficient access.  Please retry operation as root."

Additional info:
https://bugzilla.redhat.com/show_bug.cgi?id=683926.
Comment 2 Kaleem 2011-11-23 09:27:31 UTC 
Verified.

Certmonger Version:
[root@dhcp201-118 ~]# rpm -q certmonger
certmonger-0.50-1.el5
[root@dhcp201-118 ~]#

Now proper error message is displayed when non-root user runs "ipa-getcert list" command.

[root@dhcp201-118 ~]# su - testuser
[testuser@dhcp201-118 ~]$ ipa-getcert list
Insufficient access.  Please retry operation as root.
[testuser@dhcp201-118 ~]$
Comment 3 errata-xmlrpc 2012-02-21 06:17:12 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-2012-0245.html