Bug 831167 - Authentication failure between cups and pam
Authentication failure between cups and pam
Status: CLOSED DUPLICATE of bug 622333
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cups (Show other bugs)
5.7
x86_64 Unspecified
unspecified Severity medium
: rc
: ---
Assigned To: Tim Waugh
qe-baseos-daemons
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-12 07:42 EDT by Anderson Mekelburg
Modified: 2012-06-22 06:41 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-06-22 06:41:52 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Anderson Mekelburg 2012-06-12 07:42:46 EDT
Description of problem:
When I configured my cups to authenticate with Active Directory login and password, after some time working with cups web interface, I receive a popup that requires me to insert login and password. When I put my login and password the popup appears again.
In the /var/log/cups/error_log file I receive the following error:

E [12/Jun/2012:07:05:14 -0300] cupsdAuthorize: pam_authenticate() returned 7 (Authentication failure)!

And in the /var/log/secure file I receive the following error:

Jun 12 07:45:43 ServerName cupsd: pam_unix(cups:auth): authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=  user=username


Version-Release number of selected component (if applicable):
Red Hat Enterprise Linux Server release 5.7 (Tikanga)
Cups 1.3.7

How reproducible:
There's not a step-by-step to reproduce the error, it just stop to authenticate. If I use the root password it works fine.

  
Actual results:
Authentication failure

Expected results:
Authentication

Additional info:
If I restart the cups daemon (service cupsd restart), the authentication starts working again.

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