Public key infrastructure token issuance and binding
First Claim
Patent Images
1. A token issuance and binding process comprising:
- providing a plurality of tokens, each token having a unique ID number stored therein;
generating a unique public/private key pair for each token;
storing each token ID number and corresponding public key in a directory/database;
storing each private key in its respective token; and
binding a unique ID number of a user to a corresponding one of the plurality of tokens by storing said correspondence there between in the directory/database.
2 Assignments
0 Petitions
Accused Products
Abstract
A token issuance and binding process includes providing a plurality of tokens, each token having a unique ID number stored therein. A unique public/private key pair is generated for each token and each token ID number and corresponding public key is stored in a directory/database. Each private key is stored in its respective token and a unique ID number of a user is bound to a corresponding one of the plurality of tokens by storing the correspondence there between in the directory/database.
-
Citations
20 Claims
-
1. A token issuance and binding process comprising:
-
providing a plurality of tokens, each token having a unique ID number stored therein;
generating a unique public/private key pair for each token;
storing each token ID number and corresponding public key in a directory/database;
storing each private key in its respective token; and
binding a unique ID number of a user to a corresponding one of the plurality of tokens by storing said correspondence there between in the directory/database. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10)
-
-
11. A PKI (Public Key Infrastructure) system comprising:
-
a plurality of tokens, each token having a unique ID number stored therein;
a CMS (Certificate Management System) facility including a first interface to read data from said plurality of tokens and to write data to said plurality of tokens and including a directory/database; and
a badging facility including a terminal operatively connected to communicate with said CMS and including a second interface to read data from said plurality of tokens and to write data to said plurality of tokens;
wherein said CMS generates a unique public/private key pair for each token and stores each token ID number and corresponding token public key in said directory/database and stores each token private key in its respective token; and
wherein a Tokenizing Officer utilizes said terminal in said badging facility to forward a unique ID number of a user to which a particular token is to be issued along with the unique ID number of said particular token to said CMS and wherein said CMS binds the unique ID number of said user to said particular token ID number by storing the correspondence there between in said directory/database. - View Dependent Claims (12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification