Bug 204974

Summary:	"Unknown Issuer" security key inserted into the computer
Product:	Red Hat Enterprise Linux 5	Reporter:	Suzanne Hillman <shillman>
Component:	esc	Assignee:	Jack Magne <jmagne>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5.0	CC:	ohegarty, rrelyea
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-10-12 18:29: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:
Embargoed:
Bug Depends On:
Bug Blocks:	181509

Description Suzanne Hillman 2006-09-01 19:44:41 UTC

Description of problem:
After logging in with the smartcard, there is a message from esc displayed to
the screen about 'Key Inserted! "Unknown Issuer" Security Key Inserted into the
computer.'

However, if I remove and reinsert the key, it is correctly detected as being
from Veracity, Inc both on removal and insertion.

Version-Release number of selected component (if applicable):
esc-1.0.0-8.fc6
pam_pkcs11-0.5.3-14
coolkey-1.0.1-3

How reproducible:
Always

Steps to Reproduce:
1. Login (with, or without using the smartcard)
2. If you used the smartcard for logging in, it'll be immediate. If you did not,
insert the smartcard.
  
Actual results:
'Key Inserted! "Unknown Issuer" Security Key Inserted into the computer.'
displayed on the screen.

Expected results:
'Key Inserted! "Veracity, Inc" Security Key Inserted into the computer.'

Additional info:

Comment 1 Jack Magne 2006-09-08 23:58:59 UTC

This is due to the fact that when the bubble notification is issued on card
insertion for the first time, ESC is in the process of phoning home for the
Issuer information.

A couple solutions come to mind.

1. Delay the bubble notification until the answer has come back.

2. Put some other string besides "Unknown Issuer" that lets the user know this
information is being obtained. Ex. "Looking Up Issuer..".

Comment 2 Suzanne Hillman 2006-09-11 15:57:14 UTC

I like 2 better, preferably with it being updated (or shown again) once it has
figured out who the Issuer is.

Comment 4 Orla Hegarty 2006-09-14 22:27:53 UTC

All of these bugs are being marked as targeted to be fixed in beta 2. However
only a subset of these bugs will be actual beta blockers. I am marking all of
these bugs a beta 2 target milestones.

Beta Blockers reflect bugs that are critical to this beta 2 release. Flags will
be set as appropriate on a case by case basis for each critical beta blocker.

Comment 5 Jack Magne 2006-09-22 04:15:09 UTC

This issue is fixed in development. The problem had to do with the following:

1. The Javascript code execution takes place in a single thread called the UI
thread.

2. When a card is inserted I had a function that:
  A. Issued the request to phone home.
     The request to phone home then does an asynchronous http request, thus the
answer comes back later.

  B. The next statement then checked to see if we had the phone home data already.
     This is impossible since we are in the same function call. The answer , no
matter how quick, won't come back until this function exits.

3. The solution is to actually throw up the bubble notifications in the callback
function that accepts the answer from Phone Home.

I got this working locally and appears to look good for all cases.
Will be in the next build.

Comment 6 Jack Magne 2006-09-24 16:56:45 UTC

Issue resolved in Rawhide build esc-1.0.0-15 when available.

Comment 7 Jack Magne 2006-09-24 16:57:06 UTC

Issue resolved in Rawhide build esc-1.0.0-15 when available.

Comment 8 Suzanne Hillman 2006-10-10 17:32:33 UTC

Verified on 1006.2's build.