This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
Bug 182309 - inconsistencies in the AOL Key product
Summary: inconsistencies in the AOL Key product
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Certificate System
Classification: Red Hat
Component: ESC
Version: 7.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Jack Magne
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-21 18:55 UTC by Kevin Unthank
Modified: 2025-06-13 12:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:06:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   DOGTAG-2611 0 None None None 2025-06-13 12:26:06 UTC

Description Kevin Unthank 2006-02-21 18:55:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20050921 Red Hat/1.0.7-1.4.1 Firefox/1.0.7

Description of problem:
===============Customer Comments====================
I noticed some inconsistencies in the AOL Key product:
- on the Mac, the application to manage the USB token and handle  enrollment is called "ESC".  (AOL renames it to be the "AOL Key  Utility" in our installer.)
- on the Mac and PC, the security module installed into Mozilla  profiles is called "CoolKey"
- on the PC, the application and system tray icon to manage the USB  token and handle enrollment is called "ESC"
- on the PC, Outlook refers to the USB token as "OpenKey" when trying  to pick a certificate to sign/encrypt email
- on the PC, whenever a CAPI application prompts for the device's  PIN, a dialog box labeled "IA" pops up.

Using four different names ("CoolKey", "ESC", "IA", and "OpenKey" )  is confusing to users -- especially when you're trying to train them  or write documentation for them.  It also sets a dangerous precident  where users will be more likely to enter their AOL Key PIN into an  untrusted application window, we should be very consistent when  prompting for this credential.

Secondly, I would like to brand everything as "AOL Key" to make the  product consistent within our environment.
====================End Customer Comments==================

Is it possible to "brand" the various components?


Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
  - on the Mac, the application to manage the USB token and handle  enrollment is called "ESC".  (AOL renames it to be the "AOL Key  Utility" in our installer.)
- on the Mac and PC, the security module installed into Mozilla  profiles is called "CoolKey"
- on the PC, the application and system tray icon to manage the USB  token and handle enrollment is called "ESC"
- on the PC, Outlook refers to the USB token as "OpenKey" when trying  to pick a certificate to sign/encrypt email
- on the PC, whenever a CAPI application prompts for the device's  PIN, a dialog box labeled "IA" pops up.

Actual Results:  Inconsistent naming of components

Expected Results:  consistent naming of components

Additional info:

Comment 1 Kevin Unthank 2006-02-21 19:01:02 UTC
I have also noticed that when I format tokens with ESC, they are being labelled
"AOL Key". This should also be changed.



Comment 2 Chandrasekar Kannan 2006-02-21 19:06:20 UTC
this bug is being closed. All Red Hat Certificate System bugs should be
filed in raidzilla.sfbay.redhat.com. thanks.

i'll move this bug to raidzilla.


Comment 3 Chandrasekar Kannan 2006-02-21 19:10:29 UTC
this is corresponding bug # for your reference
http://raidzilla.sfbay.redhat.com/show_bug.cgi?id=58033

Comment 4 Chandrasekar Kannan 2008-08-25 23:07:45 UTC
Bug already CLOSED/VERIFIED. setting screened+ flag

Comment 5 RHEL Program Management 2025-06-12 19:18:57 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.


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