Bug 1734117

Summary:	ESC does not detect/recognize both clean and formatted (with phone home) smart cards
Product:	Red Hat Enterprise Linux 8	Reporter:	Sneha Veeranki <sveerank>
Component:	esc	Assignee:	Jack Magne <jmagne>
Status:	CLOSED ERRATA	QA Contact:	PKI QE <bugzilla-pkiqe>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	aakkiang, jmagne, mharmsen
Target Milestone:	rc
Target Release:	8.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	esc-1.1.2-11.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 15:46:21 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 Sneha Veeranki 2019-07-29 16:38:42 UTC

Description of problem:
ESC does not detect/recognize both clean and formatted (with phone home) smart cards.

Version-Release number of selected component (if applicable):
esc-1.1.2-10.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Clean a card using GP-Shell 
2. Open ESC Application and insert the smart card in the smart card reader
3. Smart card is not detected

Similarly, insert a formatted smart card (it has phone home url)
The smart card is not detected 

Actual results:
The smart card should be detected 

Expected results:
The smart card is not detected 

Additional info:

Comment 1 Jack Magne 2019-07-29 18:54:42 UTC

So is this saying that all formatted or clean cards are not detected?

Or this happens after gpshell is used to clean off a given token?

thanks,

Comment 2 Sneha Veeranki 2019-07-29 21:32:10 UTC

This issue persists with formatted Gemalto cards (cards that have a phone home url). It also occurs when a Gemalto card is cleaned using GP-Shell.

Comment 6 Sneha Veeranki 2019-11-20 16:49:48 UTC

Cleaned and formatted Gemalto cards are detected by ESC.
Version: esc-1.1.2-11.el8

Comment 8 errata-xmlrpc 2020-04-28 15:46:21 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.

https://access.redhat.com/errata/RHBA-2020:1645