Bug 201352 - default mapper order should be cn, uid,pwent
Summary: default mapper order should be cn, uid,pwent
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: pam_pkcs11 (Show other bugs)
(Show other bugs)
Version: 5.0
Hardware: All Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Bob Relyea
QA Contact:
URL:
Whiteboard:
Keywords:
: 201377 (view as bug list)
Depends On:
Blocks: 181386 181509
TreeView+ depends on / blocked
 
Reported: 2006-08-04 15:37 UTC by Bob Relyea
Modified: 2007-11-30 22:07 UTC (History)
2 users (show)

Fixed In Version: 5.0.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-11-13 14:55:10 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Bob Relyea 2006-08-04 15:37:28 UTC
Description of problem:

pam_pkcs11 uses a mapper interface to map the certificate to a unix user.
for Fedora, the default order should be:

cn - maps a cn value to a user id based on a mapping file cn_map. Basic fallback
case.
uid - maps the unix user based on the uid attribute of the DN.
pwent - used the password file to map the cn to a user id.


cn is basically a user configurable override for a given cert.
uid is a TPS override for a given user.
pwent is for environments with NIS or ldap password entries.

Comment 1 Ray Strode [halfline] 2006-08-04 22:02:14 UTC
*** Bug 201377 has been marked as a duplicate of this bug. ***

Comment 2 Bob Relyea 2006-08-29 17:18:49 UTC
pam_pkcs11-0.5.3-14

Comment 5 Bob Relyea 2006-09-13 18:04:48 UTC
Fixed in pam_pkcs11-0.5.3-15

Comment 7 Orla Hegarty 2006-09-25 22:43:44 UTC
I can confirm that the order is now correct in RHEL 5 beta 2 milestone 3 (
candidate 20060921.0 ) on both x84_64 and i396

I will verify this bug is fixed once we have a stable candidate that [1]
installs and [2] in which the pam stack preventing smart card login does not
require a workaround ( bug#207410 ) 

Comment 8 Orla Hegarty 2006-10-12 18:32:08 UTC
VERIFIED fixed against candidate RHEL5-Client-20061006.2 

$ rpm -qa | grep pam_pkcs11
pam_pkcs11-0.5.3-22
pam_pkcs11-0.5.3-22

Comment 9 Jay Turner 2006-11-13 14:55:10 UTC
Closing out as included in latest RHEL5 builds (20061111.0)


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