System and method for authorizing a new authenticator

Abstract

A system, apparatus, method, and machine readable medium are described for authorizing a new authenticator with a relying party. For example, one embodiment of a method comprises: identifying a plurality of relying parties with which an old authenticator is registered; generating at least one key for each of the plurality of relying parties; authenticating with each of the relying parties using a client having the old authenticator configured thereon, the client authorizing the new authenticator by providing an authorization object to each relying party comprising the at least one key, data identifying the new authenticator, and cryptographic data to be used by the relying party to verify the authorization object; and wherein, in response to verifying the authorization object, each relying party registers the new authenticator.

Description

BACKGROUND

1. Field of the Invention

This invention relates generally to the field of data processing systems. More particularly, the invention relates to a system and method for authorizing a new authenticator.

2. Description of Related Art

FIG. 1 illustrates an exemplary client 120 with a biometric device 100. When operated normally, a biometric sensor 102 reads raw biometric data from the user (e.g., capture the user's fingerprint, record the user's voice, snap a photo of the user, etc) and a feature extraction module 103 extracts specified characteristics of the raw biometric data (e.g., focusing on certain regions of the fingerprint, certain facial features, etc). A matcher module 104 compares the extracted features 133 with biometric reference data 110 stored in a secure storage on the client 120 and generates a score based on the similarity between the extracted features and the biometric reference data 110. The biometric reference data 110 is typically the result of an enrollment process in which the user enrolls a fingerprint, voice sample, image or other biometric data with the device 100. An application 105 may then use the score to determine whether the authentication was successful (e.g., if the score is above a certain specified threshold).

While the system shown in FIG. 1 is oriented towards biometric authentication, various other or additional authentication techniques may be employed on the exemplary client 120. For example, the client-side authenticators may be based on a PIN or other secret code (e.g., a password) entered by the user and/or may be triggered based on user presence (e.g., a button that user pushes to verify presence).

Systems have been designed for providing secure user authentication over a network using biometric sensors. In such systems, the score generated by the application, and/or other authentication data, may be sent over a network to authenticate the user with a remote server. For example, Patent Application No. 2011/0082801 (“'801 Application”) describes a framework for user registration and authentication on a network which provides strong authentication (e.g., protection against identity theft and phishing), secure transactions (e.g., protection against “malware in the browser” and “man in the middle” attacks for transactions), and enrollment/management of client authentication tokens (e.g., fingerprint readers, facial recognition devices, smartcards, trusted platform modules, etc).

The assignee of the present application has developed a variety of improvements to the authentication framework described in the '801 application. Some of these improvements are described in the following set of US Patent Applications (“Co-pending Applications”), all filed Dec. 29, 1012, which are assigned to the present assignee and incorporated herein by reference: Ser. No. 13/730,761, Query System and Method to Determine Authentication Capabilities; Ser. No. 13/730,776, System and Method for Efficiently Enrolling, Registering, and Authenticating With Multiple Authentication Devices; Ser. No. 13/730,780, System and Method for Processing Random Challenges Within an Authentication Framework; Ser. No. 13/730,791, System and Method for Implementing Privacy Classes Within an Authentication Framework; Ser. No. 13/730,795, System and Method for Implementing Transaction Signaling Within an Authentication Framework.

Briefly, the Co-Pending Applications describe authentication techniques in which a user enrolls with authentication devices (or Authenticators) such as biometric devices (e.g., fingerprint sensors) on a client device. When a user enrolls with a biometric device, biometric reference data is captured (e.g., by swiping a finger, snapping a picture, recording a voice, etc). The user may subsequently register the authentication devices with one or more servers over a network (e.g., Websites or other relying parties equipped with secure transaction services as described in the Co-Pending Applications); and subsequently authenticate with those servers using data exchanged during the registration process (e.g., cryptographic keys provisioned into the authentication devices). Once authenticated, the user is permitted to perform one or more online transactions with a Website or other relying party. In the framework described in the Co-Pending Applications, sensitive information such as fingerprint data and other data which can be used to uniquely identify the user, may be retained locally on the user's authentication device to protect a user's privacy.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present invention can be obtained from the following detailed description in conjunction with the following drawings, in which:

FIG. 1 illustrates an exemplary client equipped with a biometric device;

FIG. 2 illustrates one embodiment of a system for authorizing a new authenticator with a relying party;

FIG. 3 illustrates additional details of one embodiment of a system for authorizing a new authenticator with a relying party;

FIG. 4 illustrates one embodiment of a method for authorizing a new authenticator with a relying party;

FIG. 5 illustrates a one embodiment in which an old authenticator authorizes a new authenticator with a plurality of relying parties;

FIG. 6 illustrates one particular embodiment in which a control system controls authorization of new authenticators within an organization; and

FIGS. 7A-B illustrate exemplary system architectures on which the embodiments of the invention may be implemented.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

Described below are embodiments of an apparatus, method, and machine-readable medium for authorizing a new authenticator. Throughout the description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one skilled in the art that the present invention may be practiced without some of these specific details. In other instances, well-known structures and devices are not shown or are shown in a block diagram form to avoid obscuring the underlying principles of the present invention.

The embodiments of the invention discussed below involve authentication devices with user verification capabilities such as biometric modalities or PIN entry. These devices are sometimes referred to herein as “tokens,” “authentication devices,” or “authenticators.” While certain embodiments focus on facial recognition hardware/software (e.g., a camera and associated software for recognizing a user's face and tracking a user's eye movement), some embodiments may utilize additional biometric devices including, for example, fingerprint sensors, voice recognition hardware/software (e.g., a microphone and associated software for recognizing a user's voice), and optical recognition capabilities (e.g., an optical scanner and associated software for scanning the retina of a user). The user verification capabilities may also include non-biometric modalities, like PIN entry. The authenticators might use devices like trusted platform modules (TPMs), smartcards and secure elements for cryptographic operations and key storage.

In a mobile biometric implementation, the biometric device may be remote from the relying party. As used herein, the term “remote” means that the biometric sensor is not part of the security boundary of the computer it is communicatively coupled to (e.g., it is not embedded into the same physical enclosure as the relying party computer). By way of example, the biometric device may be coupled to the relying party via a network (e.g., the Internet, a wireless network link, etc) or via a peripheral input such as a USB port. Under these conditions, there may be no way for the relying party to know if the device is one which is authorized by the relying party (e.g., one which provides an acceptable level of authentication strength and integrity protection) and/or whether a hacker has compromised or even replaced the biometric device. Confidence in the biometric device depends on the particular implementation of the device.

The term “relying party” is sometimes used herein to refer, not merely to the entity with which a user transaction is attempted (e.g., a Website or online service performing user transactions), but also to the secure transaction servers implemented on behalf of that entity which may performed the underlying authentication techniques described herein. The secure transaction servers may be owned and/or under the control of the relying party or may be under the control of a third party offering secure transaction services to the relying party as part of a business arrangement.

The term “server” is used herein to refer to software executed on a hardware platform (or across multiple hardware platforms) that receives requests over a network from a client, responsively performs one or more operations, and transmits a response to the client, typically including the results of the operations. The server responds to client requests to provide, or help to provide, a network “service” to the clients. Significantly, a server is not limited to a single computer (e.g., a single hardware device for executing the server software) and may, in fact, be spread across multiple hardware platforms, potentially at multiple geographical locations.

System and Method for Authorizing a New Authenticator

In some instances, it may be useful to allow a new authenticator to be enabled using registered authenticators on existing client devices. For example, if the user purchases a new device with a new set of authenticators, it would be beneficial to provide the user with a way to automatically register all of the new authenticators using the existing authenticators.

The embodiments of the invention described below allow a user to authorize the authenticator(s) on a new client device using an existing/old, trusted client device that is registered with one or more relying parties. In particular, these embodiments may be used to enable new authenticators on new or existing client devices and keep the registrations in sync between multiple client devices.

FIG. 2 provides a high level overview of authenticator authorization in accordance with one embodiment of the invention. A client device with an old/existing authenticator (Aold) 202 (i.e., a device which has an authenticator which is registered with one or more relying parties 250), establishes a connection with the user's new client device 200. The particular manner in which the connection is established is not pertinent to the underlying principles of the invention. In one embodiment, the connection comprises a secure/encrypted connection (e.g., established via SSL, TLS, etc). Various techniques may be used such as near field communication (NFC), Bluetooth, Wifi Direct, using a quick response (QR) code and establishing an HTTPS connection, or over a standard network connection (e.g., via WiFi or Ethernet).

In one embodiment, once the connection is established between the client with Aold 202 and the client with Anew 200, a secure protocol is implemented (described in detail below) to transfer and integrate the registration data from the old/existing client 202 to the new client 200. For example, in one embodiment, the old client 202 sends registration data to the new client 200 which then generates a new set of key pairs (e.g., one for each relying party) and sends the public keys back to the old client 202 along with an indication of the types of authenticators on the new client 200. The client with Aold then generates a signed authorization object (e.g., using the public keys, authenticator identification data, and user account data) which it sends to each respective relying party 250.

As illustrated in FIG. 3, an authenticator authorization application 390, 391 may be executed on the new device 200 and old device 202, respectively, to establish the secure connection, exchange the authorization data, and verify the registrations with a secure transaction service 304 on each relying party 250. As used herein, an “old authenticator” (Aold) is an authenticator that a user has already registered with one or more relying parties. A “new authenticator” (Anew) is one which the user wishes to enable with all the relying party registrations currently being used with the old authenticator. Thus, the authentication engine 311 in the described embodiments has previously registered one or more old authentication devices 322-323 with a relying party. The goal of one embodiment is to transfer registrations from the old authentication engine 311 to the new authentication engine 310 to enable the new authenticators 320-321 with each relying party.

As illustrated the new client 200 and the old client 202 both include secure storage 325 and 326, respectively, for storing the registration data for each relying party (e.g., public/private key pairs used during authentication). In addition, the relying party 250 includes a secure transaction database 325 for securely storing registration data for each of the client devices 200-202 (e.g., user account data, authenticator identification data, public keys provided by for each authenticator, etc).

In one embodiment, the user initiates the authenticator authorization application 390 on the new client device 200 and the authenticator authorization application 390 on the old client device 202 to establish the initial secure connection. The authenticator authorization applications 390-391 may be mobile device apps or applications specifically designed to perform the authorization operations described herein. In another embodiment, the authenticator authorization applications may be browser plugins executed in response to the user indicating that he/she wishes to perform authorization (e.g., via a web page with embedded Javascript or other applet or executable program code). Moreover, the authenticator authorization applications 390-391 may be software modules within a larger application such as an authentication application designed to manage authentications with relying parties. It should be noted, however, that the underlying principles of the invention are not limited to any particular implementation of the authenticator authorization applications 390-391.

In one embodiment, to approve the authorization operations on the old device 202, the user is verified by the authentication engine 311 on the old device (e.g., providing biometric input to a user authentication device 322-323). Similarly, in one embodiment, the user may be verified by the authentication engine 310 on the new client device 200. These two verification steps may provide authorization for the authenticator authorization applications 390-391 to perform the authorization process.

As mentioned, at the start of the authorization process, the authenticator authorization applications 390-391 establish a secure connection (e.g., using Bluetooth, WiFi, etc). In one embodiment, the authenticator authorization application 390 on the new client device 200 receives a set of registration data for each relying party with which the old client device 202 is registered. The registration data may include usernames and a unique code associated with the user's account on each relying party. This unique code associating the user with each relying party is sometimes referred to herein as an “AppID.” In some embodiments, where a relying party offers multiple online services, a user may have multiple AppIDs with a single relying party (one for each service offered by the relying party).

In one embodiment, the authenticator authorization application 390 on the new client 200 then generates a new public/private key pair for each relying party (e.g., one for each Username+AppID pair). The authenticator authorization application 390 on the new client 200 sends the authenticator authorization application 391 on the old client 202 the key pair (or just the public key) along with an authenticator ID identifying each new authenticator type (e.g., an Authenticator Attestation ID or “AAID”). The user may then be prompted to confirm the authorization of the new authenticator(s).

In one embodiment, the authenticator authorization application 391 generates a signed authorization object comprising a signature over the tuple of the AAID, the public key and the AppID for each relying party. In one embodiment, the signature is generated using the current authentication key associated with the relying party (e.g., a private key associated with the old authenticator for the relying party). The authenticator authorization application 391 then authenticates to each of the relying parties (e.g., via the old authentication engine 311 and one or more old authenticators 322-323) and includes the signed authorization object as an extension to one of the authentication messages.

Upon receiving the signed authentication message, the secure transaction service 304 may then verify the signature (e.g., using the public key corresponding to the private key used to generate the signature). Once verified, it may identify the user's account with the AppID and store the new AAID and the new public key for the new authenticator(s) within the secure transaction database 325. The user may subsequently authenticate using the new authenticators 320-321 without re-registering with each relying party 250.

Although illustrated in FIGS. 2-3 as a new user device, the underlying principles of the invention may also be implemented in a scenario where a user installs a new authenticator on an existing client device. For example, the user may upgrade or add an authenticator to an existing desktop, notebook or other type of client. In such a case, the communication of between the authenticator authorization applications 390-391 shown in FIG. 3 may occur internally (e.g., via internal function calls between software modules implemented on the client).

One embodiment of a method for authorizing a new authenticator is illustrated in FIG. 4. The method may be implemented within the context of a system such as shown in FIG. 3, but is not limited to any particular system architecture.

At 401, the user triggers the authorization of one or more new authenticators (Anew) and establishes a secure communication channel with the old authenticator(s) (Aold). As mentioned, the secure communication channel may be established via a direct connection (e.g., via NFC, Bluetooth, etc) or over a network (e.g., via an Ethernet or WiFi connection).

At 402, the new authenticator receives a username and user/relying party ID code for each relying party.

At 403, the new authenticator generates a public/private key pair for each username/AppID pair (e.g., for each unique relying party account).

At 404, the old authenticator receives the key pairs and an authenticator attestation ID code identifying the type of each new authenticator (e.g., an AAID). The user may then be asked to confirm the authorization operation.

At 405, the old authenticator generates a signed authorization object comprising a signature over the tuple of the AAID, the public key and the AppID for each relying party. As mentioned, the signature may be generated using the current authentication key associated with the relying party (e.g., a private key associated with the old authenticator for the relying party).

At 406, the old authenticator authenticates to each relying party and includes the signed authorization object as an extension to the authentication message. Once this operation is successfully completed, the user may then authenticate with each relying party using the new device and/or new authenticators.

FIG. 5 graphically illustrates a sequence of operations in which a new authenticator 501 is authorized for use with a plurality of relying parties R1-Rn using an old authenticator 502 on an old client 500. As mentioned, after receiving account data related to each of the relying parties, the new authenticator 501 generates new key pairs for each of the relying parties R1-Rn and provides the new key pairs to the old authenticator 502. The old authenticator 502 then generates a secure authorization object containing data related to the new authenticator 501 (e.g., the AAID) and a new key for each authenticator. It then performs authentication with each of the relying parties R1-Rn and includes the authentication object. Following verification (e.g., in which a signature on the authorization object is verified), the new authenticator 501 is automatically registered at each relying party R1-Rn.

In one embodiment, each relying party R1-Rn can choose whether or not to accept the new authenticator 501. For example, if the AAID indicates an authenticator type which is not sufficiently reliable or accurate, then the relying party may choose to deny the new registration. Thus, each relying party may maintain an authenticator database (i.e., Metadata) containing data for all known authenticators (e.g., identified by AAID). It may then query the database in response to receiving the authorization object from the old authenticator, determine the characteristics of the new authenticator, and determine whether those characteristics are acceptable.

In one embodiment of the invention, an authenticator can specify a more generic “confirmation” method, where the authenticators may be indirectly controlled by the same entity, but still belong to different users. For example, in FIG. 6, the old authenticator 601 might be integrated into an Owner Control System 601 controlled by a single owner/operator (e.g., a corporation or government entity). The new authenticator 612 in this example may be authenticator belonging to a staff computer 611 and authorization of the new authenticator 612 may be trigger by the owner control system 601 using a known trusted authenticator 602. In this example, the interactions between the new authenticator 612 and old authenticator 602 may be as described above (e.g., the new authenticator generating new key pairs and the old authenticator sending an authorization object to a device 621 comprising an owner or vendor trust anchor 622 (e.g., for storing authenticator registration data as does the secure transaction database 325 of the secure transaction service 304 in FIG. 3).

Exemplary System Architectures

It should be noted that the term “relying party” is used herein to refer, not merely to the entity with which a user transaction is attempted (e.g., a Website or online service performing user transactions), but also to the secure transaction servers implemented on behalf of that entity which may perform the underlying authentication techniques described herein. The secure transaction servers may be owned and/or under the control of the relying party or may be under the control of a third party offering secure transaction services to the relying party as part of a business arrangement. These distinctions are indicated in FIGS. 7A-B discussed below which show that the “relying party” may include Websites 731 and other network services 751 as well as the secure transaction servers 732-733 for performing the authentication techniques on behalf of the websites and network services.

In particular, FIGS. 7A-B illustrate two embodiments of a system architecture comprising client-side and server-side components for authenticating a user. The embodiment shown in FIG. 7A uses a browser plugin-based architecture for communicating with a website while the embodiment shown in FIG. 7B does not require a browser. The various user confirmation and authorization techniques described herein may be employed on either of these system architectures. For example, the authentication engines 310, 311 and authenticator authorization applications 390, 391 may be implemented as part of the secure transaction service 701 including interface 702. It should be noted, however, that the embodiments described above may be implemented using logical arrangements of hardware and software other than those shown in FIGS. 7A-B.

Turning to FIG. 7A, the illustrated embodiment includes a client 700 equipped with one or more authentication devices 710-712 for enrolling and authenticating an end user. As mentioned above, the authentication devices 710-712 may include biometric devices such as fingerprint sensors, voice recognition hardware/software (e.g., a microphone and associated software for recognizing a user's voice), facial recognition hardware/software (e.g., a camera and associated software for recognizing a user's face), and optical recognition capabilities (e.g., an optical scanner and associated software for scanning the retina of a user) and non-biometric devices such as a trusted platform modules (TPMs) and smartcards. A user may enroll to the biometric devices by providing biometric data (e.g., swiping a finger on the fingerprint device) which the secure transaction service 701 may store as biometric template data in secure storage 720 (via interface 702).

While the secure storage 720 is illustrated outside of the secure perimeter of the authentication device(s) 710-712, in one embodiment, each authentication device 710-712 may have its own integrated secure storage. Additionally, each authentication device 710-712 may cryptographically protect the biometric reference data records (e.g., wrapping them using a symmetric key to make the storage 720 secure).

The authentication devices 710-712 are communicatively coupled to the client through an interface 702 (e.g., an application programming interface or API) exposed by a secure transaction service 701. The secure transaction service 701 is a secure application for communicating with one or more secure transaction servers 732 over a network and for interfacing with a secure transaction plugin 705 executed within the context of a web browser 704. As illustrated, the Interface 702 may also provide secure access to a secure storage device 720 on the client 700 which stores information related to each of the authentication devices 710-712 such as a device identification code, user identification code, user enrollment data (e.g., scanned fingerprint or other biometric data), and keys used to perform the secure authentication techniques described herein. For example, as discussed in detail below, a unique key may be stored into each of the authentication devices during registration and used when communicating to servers 730 over a network such as the Internet.

Once the user has enrolled with an authentication device on the client 700, the secure transaction service 701 may register the authentication device with the secure transaction servers 732-733 over the network (e.g., using the registration techniques described herein) and subsequently authenticate with those servers using data exchanged during the registration process (e.g., encryption keys provisioned into the biometric devices). The authentication process may include any of the authentication techniques described herein (e.g., generating an assurance level on the client 700 based on explicit or non-intrusive authentication techniques and transmitting the results to the secure transaction servers 732-733).

As discussed below, certain types of network transactions are supported by the secure transaction plugin 705 such as HTTP or HTTPS transactions with websites 731 or other servers. In one embodiment, the secure transaction plugin is initiated in response to specific HTML tags inserted into the HTML code of a web page by the web server 731 within the secure enterprise or Web destination 730 (sometimes simply referred to below as “server 730”). In response to detecting such a tag, the secure transaction plugin 705 may forward transactions to the secure transaction service 701 for processing. In addition, for certain types of transactions (e.g., such as secure key exchange) the secure transaction service 701 may open a direct communication channel with the on-premises transaction server 732 (i.e., co-located with the website) or with an off-premises transaction server 733.

The secure transaction servers 732-733 are coupled to a secure transaction database 740 for storing user data, authentication device data, keys and other secure information needed to support the secure authentication transactions described below. It should be noted, however, that the underlying principles of the invention do not require the separation of logical components within the secure enterprise or web destination 730 shown in FIG. 7A. For example, the website 731 and the secure transaction servers 732-733 may be implemented within a single physical server or separate physical servers. Moreover, the website 731 and transaction servers 732-733 may be implemented within an integrated software module executed on one or more servers for performing the functions described below.

As mentioned above, the underlying principles of the invention are not limited to a browser-based architecture shown in FIG. 7A. FIG. 7B illustrates an alternate implementation in which a stand-alone application 754 utilizes the functionality provided by the secure transaction service 701 to authenticate a user over a network. In one embodiment, the application 754 is designed to establish communication sessions with one or more network services 751 which rely on the secure transaction servers 732-733 for performing the user/client authentication techniques described in detail below.

In either of the embodiments shown in FIGS. 7A-B, the secure transaction servers 732-733 may generate the keys which are then securely transmitted to the secure transaction service 701 and stored into the authentication devices within the secure storage 720. Additionally, the secure transaction servers 732-733 manage the secure transaction database 740 on the server side.

Embodiments of the invention may include various steps as set forth above. The steps may be embodied in machine-executable instructions which cause a general-purpose or special-purpose processor to perform certain steps. Alternatively, these steps may be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.

Elements of the present invention may also be provided as a machine-readable medium for storing the machine-executable program code. The machine-readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, or other type of media/machine-readable medium suitable for storing electronic program code.

Throughout the foregoing description, for the purposes of explanation, numerous specific details were set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention may be practiced without some of these specific details. For example, it will be readily apparent to those of skill in the art that the functional modules and methods described herein may be implemented as software, hardware or any combination thereof. Moreover, although some embodiments of the invention are described herein within the context of a mobile computing environment, the underlying principles of the invention are not limited to a mobile computing implementation. Virtually any type of client or peer data processing devices may be used in some embodiments including, for example, desktop or workstation computers. Accordingly, the scope and spirit of the invention should be judged in terms of the claims which follow.

Claims

1. A method for authorizing a new authenticator comprising: identifying a plurality of relying parties with which an old authenticator is registered;generating at least one key for each of the plurality of relying parties;authenticating with each of the relying parties using a client having the old authenticator configured thereon, the client authorizing the new authenticator by providing an authorization object to each relying party comprising the at least one key, data identifying the new authenticator, and cryptographic data to be used by the relying party to verify the authorization object;wherein, in response to verifying the authorization object, each relying party registers the new authenticator;wherein an operation of generating at least one key is performed by the new authenticator;wherein identifying the plurality of relying parties comprises the new authenticator receiving a list of usernames and unique identification codes to identify each relying party from the old authenticator; andestablishing a secure communication channel between the old authenticator and the new authenticator, wherein the new authenticator receives the list of usernames and unique identification codes to identify each relying party from the old authenticator over the secure communication channel.

2. The method as in claim 1 wherein the data identifying the new authenticator comprises an Authenticator Attestation ID (AAID).

3. The method as in claim 1, wherein the authorization object further comprises a first unique identification code identifying the relying party's service.

4. The method as in claim 1 wherein the authorization object further comprises a Username or UserID identifying a user account at each relying party.

5. The method as in claim 4 wherein generating at least one key comprises generating a public/private key pair for each relying party and wherein the public key of the key pair is provided in the authorization object to the relying party.

6. The method as in claim 1 wherein the cryptographic data comprises a signature generating using a private key of the old authenticator.

7. The method as in claim 6 wherein the signature is generated over contents of the authorization object.

8. The method as in claim 1 wherein generating at least one key comprises the new authenticator generating a public/private key pair for each pair of the username and unique identification codes to identify each relying party.

9. The method as in claim 1 wherein the old authenticator is configured within a control system managed by an organization, the new authenticator is configured within a staff computer of the organization, and the relying party comprises a trust anchor managed by the organization.

10. The method as in claim 1 wherein the secure communication channel comprises a Bluetooth channel, Near Field Communication channel, WiFi channel, or Ethernet channel.

11. The method as in claim 1 wherein the old authenticator (Aold) displays the unique identification code for a first relying party and a public key hash of the key on a secure display used for transaction confirmation operations and wherein the new authenticator (Anew) displays the public key hash derived from a public key extracted from an authenticated message received from Aold and also displays the unique identification code for the first relying part and the public key hash on its secure display, thereby allowing the user to verify the correctness of the operation even in the case of compromised client devices.

12. A non-transitory machine-readable medium having program code stored thereon which, when executed by one or more computing devices, causes the one or more computing devices to perform the operations of: identifying a plurality of relying parties with which an old authenticator is registered;generating at least one key for each of the plurality of relying parties;authenticating with each of the relying parties using a client having the old authenticator configured thereon, the client authorizing the new authenticator by providing an authorization object to each relying party comprising the at least one key, data identifying the new authenticator, and cryptographic data to be used by the relying party to verify the authorization object; andwherein, in response to verifying the authorization object, each relying party registers the new authenticator;wherein an operation of generating at least one key is performed by the new authenticator;wherein identifying the plurality of relying parties comprises the new authenticator receiving a list of usernames and unique identification codes identifying each relying party from the old authenticator; andestablishing a secure communication channel between the old authenticator and the new authenticator, wherein the new authenticator receives the list of usernames and unique identification codes identifying each relying party from the old authenticator over the secure communication channel.

13. The non-transitory machine-readable medium as in claim 12 wherein the data identifying the new authenticator comprises an Authenticator Attestation ID (AAID).

14. The non-transitory machine readable-medium as in claim 12, wherein the authorization object further comprises a first unique identification code identifying the relying party's service.

15. The non-transitory machine-readable medium as in claim 12 wherein the authorization object further comprises a username/UserID identifying a user account at each relying party.

16. The non-transitory machine-readable medium as in claim 15 wherein generating at least one key comprises generating a public/private key pair for each relying party and wherein the public key of the key pair is provided in the authorization object to the relying party.

17. The non-transitory machine-readable medium as in claim 12 wherein the cryptographic data comprises a signature generating using a private key of the old authenticator.

18. The non-transitory machine-readable medium as in claim 17 wherein the signature is generated over contents of the authorization object.

19. The non-transitory machine-readable medium as in claim 12 wherein generating at least one key comprises the new authenticator generating a public/private key pair for each pair of the username and unique identification codes to identify each relying party.

20. The non-transitory machine-readable medium as in claim 12 wherein the old authenticator is configured within a control system managed by an organization, the new authenticator is configured within a staff computer of the organization, and the relying party comprises a trust anchor managed by the organization.

21. The non-transitory machine-readable medium as in claim 12 wherein the secure communication channel comprises a Bluetooth channel, Near Field Communication channel, WiFi channel, or Ethernet channel.

22. The non-transitory machine-readable medium as in claim 12 wherein the old authenticator (Aold) displays the unique identification code for a first relying party and a public key hash of the key on a secure display used for transaction confirmation operations and wherein the new authenticator (Anew) displays the public key hash derived from a public key extracted from an authenticated message received from Aold and also displays the unique identification code for the first relying part and the public key hash on its secure display, thereby allowing the user to verify the correctness of the operation even in the case of compromised client devices.

23. A method for authorizing a new authenticator comprising: identifying a plurality of relying parties with which an old authenticator is registered;generating at least one key for each of the plurality of relying parties;authenticating with each of the relying parties using a client having the old authenticator configured thereon, the client authorizing the new authenticator by providing an authorization object to each relying party comprising the at least one key, data identifying the new authenticator, and cryptographic data to be used by the relying party to verify the authorization object;wherein, in response to verifying the authorization object, each relying party registers the new authenticator;wherein the operation of generating at least one key is performed by the new authenticator;wherein identifying the plurality of relying parties comprises the new authenticator receiving a list of usernames and unique identification codes to identify each relying party from the old authenticator; andwherein generating at least one key comprises the new authenticator generating a public/private key pair for each pair of the username and unique identification codes to identify each relying party.

24. A non-transitory machine-readable medium having program code stored thereon which, when executed by one or more computing devices, causes the one or more computing devices to perform the operations of: identifying a plurality of relying parties with which an old authenticator is registered;generating at least one key for each of the plurality of relying parties;authenticating with each of the relying parties using a client having the old authenticator configured thereon, the client authorizing the new authenticator by providing an authorization object to each relying party comprising the at least one key, data identifying the new authenticator, and cryptographic data to be used by the relying party to verify the authorization object; andwherein, in response to verifying the authorization object, each relying party registers the new authenticator;wherein the operation of generating at least one key is performed by the new authenticator;wherein identifying the plurality of relying parties comprises the new authenticator receiving a list of usernames and unique identification codes to identify each relying party from the old authenticator; andwherein generating at least one key comprises the new authenticator generating a public/private key pair for each pair of the username and unique identification code to identify each relying party.