Bug 1462000

Summary:	Smartcard pin prompt on GDM has a different username than on the card
Product:	Red Hat Enterprise Linux 7	Reporter:	Roshni <rpattath>
Component:	opensc	Assignee:	Jakub Jelen <jjelen>
Status:	CLOSED DUPLICATE	QA Contact:	Asha Akkiangady <aakkiang>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	adam.winberg, jstodola, nmavrogi
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-09-04 07:40:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Roshni 2017-06-15 21:40:41 UTC

Description of problem:
Smartcard pin prompt on GDM has a different username than on the card

Version-Release number of selected component (if applicable):
opensc-0.16.0-5.20170227git777e2a3.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1. Enable "Require smartcard for login" using authconfig
2. Rebbot
3.

Actual results:
GDM login screen has message "Welcome PIN1 (ID-kaart)!" instead of user on the card

Expected results:


Additional info:
Removing and re-inserting the card shows the correct username

Comment 2 Jakub Jelen 2017-06-16 12:18:38 UTC

This is directly related to the bug #1449740 which talks about different card labels. It is also wrong assumption from GDM that the label will contain some username.

What we can do:
 * Resolve the bug #1449740 in OpenSC to mimic the Coolkey labels: would need to discuss upstream. This is a change of the labels and therefore in the PKCS#11 URI, which might not be welcomed
 * Not show this message in GDM

I don't think there is some other reasonable way how to get the user of the card from PKCS#11.

I will raise a question on the upstream mailing list if the first solution would be acceptable and it could make it to the next release.

Comment 3 Jakub Jelen 2017-09-04 07:40:57 UTC


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