CA2345148A1 - Method for the separate authentication of a template and user data - Google Patents
Method for the separate authentication of a template and user data Download PDFInfo
- Publication number
- CA2345148A1 CA2345148A1 CA002345148A CA2345148A CA2345148A1 CA 2345148 A1 CA2345148 A1 CA 2345148A1 CA 002345148 A CA002345148 A CA 002345148A CA 2345148 A CA2345148 A CA 2345148A CA 2345148 A1 CA2345148 A1 CA 2345148A1
- Authority
- CA
- Canada
- Prior art keywords
- dac
- template
- user data
- generating
- hereinafter referred
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6209—Protecting access to data via a platform, e.g. using keys or access control rules to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2147—Locking files
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Health & Medical Sciences (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Bioethics (AREA)
- Document Processing Apparatus (AREA)
- Storage Device Security (AREA)
Abstract
A method for the separate authentication of a template and of data inserted therein. A template is provided with a template ID and a template Data Authentication Code (DAC(t)). User data is inserted in the template, and the n extracted to be handled separately. A DAC(d) is generated on the user data b y itself, and stored in an Approval Data packet with the template ID, DAC(t) a nd the user data. The complete document with the template and the user data can later be reconstructed. The method may be useful for many industries that re ly on templates as a means for collecting data.
Claims (25)
1. A method for the separate authentication of a template and of user data inserted therein, comprising the steps of:
a) providing the template, said template having a corresponding template ID
and template Document Authentication Code, hereinafter referred to as DAC(t), linked thereto;
b) inserting the user data in the template;
c) extracting the user data from the template;
d) generating a user data Document Authentication Code, hereinafter referred to as DAC(d), based on the user data; and e) storing the template ID, DAC(t), the user data and DAC(d) in an Approval Data Packet, hereinafter referred to as ADP.
a) providing the template, said template having a corresponding template ID
and template Document Authentication Code, hereinafter referred to as DAC(t), linked thereto;
b) inserting the user data in the template;
c) extracting the user data from the template;
d) generating a user data Document Authentication Code, hereinafter referred to as DAC(d), based on the user data; and e) storing the template ID, DAC(t), the user data and DAC(d) in an Approval Data Packet, hereinafter referred to as ADP.
2. The method according to claim 1, wherein step a) comprises the substeps of:
i) generating the template;
ii) creating the template ID;
iii) creating DAC(t); and iv) storing the template ID and DAC(t) in a location linked to the template.
i) generating the template;
ii) creating the template ID;
iii) creating DAC(t); and iv) storing the template ID and DAC(t) in a location linked to the template.
3. The method according to claim 2, wherein substep a)iii) comprises generating DAC(t) from a one-way hash function.
4. The method according to claim 2, wherein, in substep a) iv), the location linked to the template is inside said template.
5. The method according to claim 2, wherein, in substep a) iv), the location linked to the template is a linked storage system.
6. The method according to claim 1, wherein step e) further comprises encrypting the ADP.
7. The method according to claim 1, further comprising an additional step f) of reconstructing an authenticated complete document, said complete document including the template and the user data.
8. The method according to claim 7, wherein step f) comprises the substeps of:
i) retrieving the template ID and DAC(t) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d); and viii) inserting the user data in the template.
i) retrieving the template ID and DAC(t) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d); and viii) inserting the user data in the template.
9. The method according to claim 1, wherein the template has entry fields, and wherein said step of inserting user data includes the step of inserting user data into said entry fields.
10. The method according to claim 9, wherein step b) further comprises prompting the user for the user data.
11. The method according to claim 9, wherein step e) further comprises encrypting the ADP.
12. The method according to claim 9, further comprising an additional step f) of reconstructing an authenticated complete document, said complete document including the template and the user data.
13. The method according to claim 12, wherein step f) comprises the substeps of:
i) retrieving the template ID and DAC(t) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d); and viii) inserting the user data in the template.
i) retrieving the template ID and DAC(t) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d); and viii) inserting the user data in the template.
14. The method according to claim 1, wherein said method further includes step b1) generating a complete Document Authentication Code, hereinafter referred to as DAC(c), based on the template with the user data therein.
15. The method according to claim 14, wherein step a) comprises the substeps of:
i) generating the template;
ii) creating the template ID;
iii) creating DAC(t); and iv) storing the template ID and DAC(t) in a location linked to the template.
i) generating the template;
ii) creating the template ID;
iii) creating DAC(t); and iv) storing the template ID and DAC(t) in a location linked to the template.
16. The method according to claim 15, wherein substep a)iii) comprises generating DAC(t) from a one-way hash function.
17. The method according to claim 15, wherein, in substep a) iv), the location linked to the template is inside said template.
18. The method according to claim 15, wherein, in substep a) iv), the location linked to the template is a linked storage system.
19. The method according to claim 14, wherein step f) further comprises encrypting the ADP.
20. The method according to claim 14, further comprising an additional step g) of reconstructing an authenticated complete document, said complete document including the template and the user data.
21. The method according to claim 20, wherein step g) comprises the substeps of:
i) retrieving the template ID, DAC(t) and DAC(c) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d);
viii) inserting the user data in the template;
ix) generating for the template with the user data therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc); and x) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c).
i) retrieving the template ID, DAC(t) and DAC(c) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d);
viii) inserting the user data in the template;
ix) generating for the template with the user data therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc); and x) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c).
22. The method according to claim 20, wherein step g) comprises the substeps of:
i) retrieving the template ID, the user data and DAC(c) from the ADP;
ii) opening the template corresponding to said template ID;
iii) inserting the user data in the template;
iv) generating for the template with the user data therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc); and v) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c).
i) retrieving the template ID, the user data and DAC(c) from the ADP;
ii) opening the template corresponding to said template ID;
iii) inserting the user data in the template;
iv) generating for the template with the user data therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc); and v) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c).
23. A method for the separate authentication of a template and of user data inserted therein by multiple users, comprising the steps of:
a) authenticating a template and user data from a first user according to the method of claim 14; and b) for each subsequent user of the multiple users, performing the substeps of:
i) retrieving the template and DAC(c);
ii) inserting user data from previous users in the template;
iii)generating for the template with the user data from previous users therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc);
iv) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c);
v) inserting data from the current user in the template;
vi) generating a DAC(c), based on the template with the user data from the previous users and current user therein;
vii) extracting the user data from the previous users and current user from the template;
viii) generating a DAC(d), based on the user data extracted in step vii); and ix) storing the user data, DAC(c) and DAC(d) in ADP.
a) authenticating a template and user data from a first user according to the method of claim 14; and b) for each subsequent user of the multiple users, performing the substeps of:
i) retrieving the template and DAC(c);
ii) inserting user data from previous users in the template;
iii)generating for the template with the user data from previous users therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc);
iv) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c);
v) inserting data from the current user in the template;
vi) generating a DAC(c), based on the template with the user data from the previous users and current user therein;
vii) extracting the user data from the previous users and current user from the template;
viii) generating a DAC(d), based on the user data extracted in step vii); and ix) storing the user data, DAC(c) and DAC(d) in ADP.
24. The method according to claim 23, further comprising an additional step c) of reconstructing an authenticated complete document, said complete document including the template and the user data from all of the multiple users.
25. The method according to claim 24, wherein step c) comprises the substeps of:
i) retrieving the template ID, DAC(t) and DAC(c) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d);
viii) inserting the user data in the template;
ix) generating for the template with the user data therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc); and x) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c).
i) retrieving the template ID, DAC(t) and DAC(c) from the ADP;
ii) opening the template corresponding to said template ID;
iii) generating for said template a new template Document Authentication Code, hereinafter referred to as DAC(nt);
iv) comparing DAC(nt) with DAC(t), and proceeding only if DAC(nt) is equal to DAC(t);
v) retrieving the user data and DAC(d) from the ADP;
vi) generating for said user data a new user data Document Authentication Code, hereinafter referred to as DAC(nd);
vii) comparing DAC(nd) with DAC(d), and proceeding only if DAC(nd) is equal to DAC(d);
viii) inserting the user data in the template;
ix) generating for the template with the user data therein a new complete document Document Authentication Code, hereinafter referred to as DAC(nc); and x) comparing DAC(nc) with DAC(c), and proceeding only if DAC(nc) is equal to DAC(c).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA2345148A CA2345148C (en) | 1998-09-25 | 1999-09-24 | Method for the separate authentication of a template and user data |
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002246006A CA2246006A1 (en) | 1998-09-25 | 1998-09-25 | Remote template approvals in a distributed network environment |
| CA2,246,006 | 1998-09-25 | ||
| PCT/CA1999/000891 WO2000019296A1 (en) | 1998-09-25 | 1999-09-24 | Method for the separate authentication of a template and user data |
| CA2345148A CA2345148C (en) | 1998-09-25 | 1999-09-24 | Method for the separate authentication of a template and user data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2345148A1 true CA2345148A1 (en) | 2000-04-06 |
| CA2345148C CA2345148C (en) | 2010-12-14 |
Family
ID=25680442
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA2345148A Expired - Lifetime CA2345148C (en) | 1998-09-25 | 1999-09-24 | Method for the separate authentication of a template and user data |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2345148C (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP1412868A1 (en) * | 2001-07-27 | 2004-04-28 | Digital Doors, Inc. | Computer software product for data security of sensitive words characters or icons |
| US7546334B2 (en) | 2000-11-13 | 2009-06-09 | Digital Doors, Inc. | Data security system and method with adaptive filter |
| US7552482B2 (en) | 2000-11-13 | 2009-06-23 | Digital Doors, Inc. | Data security system and method |
| US7669051B2 (en) | 2000-11-13 | 2010-02-23 | DigitalDoors, Inc. | Data security system and method with multiple independent levels of security |
| US8176563B2 (en) | 2000-11-13 | 2012-05-08 | DigitalDoors, Inc. | Data security system and method with editor |
| US8423565B2 (en) | 2006-12-21 | 2013-04-16 | Digital Doors, Inc. | Information life cycle search engine and method |
| US8677505B2 (en) | 2000-11-13 | 2014-03-18 | Digital Doors, Inc. | Security system with extraction, reconstruction and secure recovery and storage of data |
| US9015301B2 (en) | 2007-01-05 | 2015-04-21 | Digital Doors, Inc. | Information infrastructure management tools with extractor, secure storage, content analysis and classification and method therefor |
| US9734169B2 (en) | 2007-01-05 | 2017-08-15 | Digital Doors, Inc. | Digital information infrastructure and method for security designated data and with granular data stores |
-
1999
- 1999-09-24 CA CA2345148A patent/CA2345148C/en not_active Expired - Lifetime
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7721344B2 (en) | 2000-11-13 | 2010-05-18 | Digital Doors, Inc. | Data security system and method |
| US7546334B2 (en) | 2000-11-13 | 2009-06-09 | Digital Doors, Inc. | Data security system and method with adaptive filter |
| US7552482B2 (en) | 2000-11-13 | 2009-06-23 | Digital Doors, Inc. | Data security system and method |
| US7669051B2 (en) | 2000-11-13 | 2010-02-23 | DigitalDoors, Inc. | Data security system and method with multiple independent levels of security |
| US7721345B2 (en) | 2000-11-13 | 2010-05-18 | Digital Doors, Inc. | Data security system and method |
| US7958268B2 (en) | 2000-11-13 | 2011-06-07 | Digital Doors, Inc. | Data security system and method adjunct to a browser, telecom or encryption program |
| US8176563B2 (en) | 2000-11-13 | 2012-05-08 | DigitalDoors, Inc. | Data security system and method with editor |
| US8677505B2 (en) | 2000-11-13 | 2014-03-18 | Digital Doors, Inc. | Security system with extraction, reconstruction and secure recovery and storage of data |
| EP1412868A4 (en) * | 2001-07-27 | 2008-01-02 | Digital Doors Inc | Computer software product for data security of sensitive words characters or icons |
| EP1412868A1 (en) * | 2001-07-27 | 2004-04-28 | Digital Doors, Inc. | Computer software product for data security of sensitive words characters or icons |
| US8423565B2 (en) | 2006-12-21 | 2013-04-16 | Digital Doors, Inc. | Information life cycle search engine and method |
| US9015301B2 (en) | 2007-01-05 | 2015-04-21 | Digital Doors, Inc. | Information infrastructure management tools with extractor, secure storage, content analysis and classification and method therefor |
| US9734169B2 (en) | 2007-01-05 | 2017-08-15 | Digital Doors, Inc. | Digital information infrastructure and method for security designated data and with granular data stores |
Also Published As
| Publication number | Publication date |
|---|---|
| CA2345148C (en) | 2010-12-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| MXPA05003546A (en) | A challenged-based tag authentication model. | |
| US6934845B2 (en) | Method and system of reversibly marking a text document with a pattern of extra blanks for authentication | |
| CN1133935C (en) | Security system for protecting information stored in portable storage media | |
| CA2068488A1 (en) | Hybrid public key algorithm/data encryption algorithm key distribution method based on control vectors | |
| DE60129682T2 (en) | UNIQUE PAD ENCRYPTION WITH CENTRAL KEY SERVICE AND CLEARABLE SIGNS | |
| US20100169665A1 (en) | Method for indexing encrypted column | |
| WO2003041324A3 (en) | Biometrics template | |
| EP2247106A3 (en) | A method and apparatus for accessing stored digital programs | |
| EP0840478A3 (en) | Digital signature generating/verifying method and system using public key encryption | |
| EP0746126A3 (en) | System for data copyright management using key distribution | |
| CN101039185B (en) | Method for resolving expandable label language in safety application of expandable label language | |
| EP0898216A3 (en) | Method for securely communicating remote control commands in a computer network | |
| HUE025028T2 (en) | Method and system for automatically logging in client | |
| CA2345148A1 (en) | Method for the separate authentication of a template and user data | |
| EP1391802A3 (en) | Saving and retrieving data based on symmetric key encryption | |
| ATE354223T1 (en) | METHOD AND DEVICE FOR INFORMATION PROCESSING | |
| CN110611662B (en) | Attribute-based encryption-based fog collaborative cloud data sharing method | |
| CN104750784B (en) | A kind of space querying integrity verification method based on Merkle tree constructions | |
| TW431105B (en) | Method for strongly authenticating another process in a different address space | |
| ATE246429T1 (en) | DATABASE GENERATION SYSTEM FOR ENCRYPTED PROGRAM MATERIAL | |
| CN114679271A (en) | Block chain private data access control method and system | |
| CN110768797A (en) | Data desensitization method based on identity format reserved encryption | |
| EP1039671A3 (en) | Methods, system and computer program for encryption of computer telephony | |
| US7272722B2 (en) | Method for industrially changing the passwords of AIX/UNIX users | |
| EP1431860A3 (en) | Information protection |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKEX | Expiry |
Effective date: 20190924 |