Method and System for Obtaining Digital Signatures

• US 20060190734A1
• Filed: 04/28/2006
• Published: 08/24/2006
• Est. Priority Date: 01/23/2001
• Status: Active Grant

• Current Assignee: Google LLC (Alphabet Inc.)
• Original Assignee: Computer Associates Think Inc. (Broadcom, Inc.)
• Inventors: Spitz, Charles F.
• Granted Patent: US 8,103,867 B2
• Time in Patent Office: Days
• US Class Current: 713/176
• CPC Class Codes: H04L 2209/68 Special signature format, e.g. XML format
• CPC Class Codes: H04L 9/3247 involving digital signatures

Abstract

A digital signature system includes a database holding access control rules that identify documents authorized users are allowed to have electronically signed and a signing system capable of receiving signature requests from a plurality of authorized users, each signature request including a document to be signed, wherein the signing system parses the document to be signed and compares information obtained thereby to the access control rules stored in the database to determine whether the authorized user is authorized to have the document signed, and wherein if it is determined that the authorized user is authorized to have the document signed, the signing system signs the document using authentication information unique to the signing system.

Claims

1. (canceled)

2. (canceled)

3. (canceled)

4. (canceled)

5. (canceled)

6. (canceled)

7. (canceled)

8. (canceled)

9. (canceled)

10. (canceled)

11. (canceled)

12. (canceled)

13. (canceled)

14. (canceled)

15. (canceled)

16. (canceled)

17. (canceled)

18. (canceled)

19. (canceled)

20. (canceled)

21. (canceled)

22. (canceled)

23. (canceled)

24. (canceled)

25. (canceled)

26. (canceled)

27. (canceled)

28. (canceled)

29. (canceled)

30. (canceled)

31. (canceled)

32. (canceled)

33. (canceled)

34. (canceled)

35. (canceled)

36. (canceled)

37. (canceled)

38. (canceled)

39. (canceled)

40. A method of digitally signing a document with a digital signature, comprising:

receiving a signature request from a requester, the signature request requesting that a document be signed;

accessing one or more signing policies of an organization, the one or more signing policies identifying a plurality of authorized users of the organization, the one or more signing policies identifying one or more document types that an authorized user is authorized to sign;

determining whether the requester is an authorized user authorized to sign the document according to the one or more signing policies; and

signing the document with an organization digital signature generated using an organization private key associated with the organization, if the requestor is an authorized user authorized to sign the document.

41. The method of claim 40, wherein:

accessing the one or more signing policies of the organization further comprises;

accessing the one or more signing policies, the one or more signing policies identifying the one or more document types that an authorized user is authorized to sign by specifying one or more attributes of the one or more document types that the authorized user is authorized to sign; and

determining whether the requester is an authorized user authorized to sign the document according to the one or more signing policies further comprises;

establishing one or more attributes of the document; and

determining whether the one or more attributes of the document match the one or more attributes of the one or more document types that the authorized user is authorized to sign.

42. The method of claim 40, wherein receiving the signature request from the requestor further comprises:

receiving the signature request, the signature request signed with a requestor digital signature generated using a requestor private key; and

verifying the signature request using a requestor public key corresponding to the requestor private key.

43. The method of claim 40, further comprising:

signing the signed document with a sender digital signature generated using a sender private key, the signed document operable to be verified with a sender public key corresponding to the sender private key.

44. The method of claim 40, wherein the signed document is operable to be verified using an organization public key corresponding to the organization private key.

45. The method of claim 40, wherein the organization private key is operable to be authenticated by a certificate authority.

46. The method of claim 40, further comprising:

sending the signed document to a recipient, the recipient distinct from the plurality of authorized users.

47. The method of claim 40, wherein:

the organization comprises a company; and

the plurality of authorized users comprise a plurality of employees of the company.

48. A system for digitally signing a document with a digital signature, comprising:

a database operable to;

store one or more signing policies of an organization, the one or more signing policies identifying a plurality of authorized users of the organization, the one or more signing policies identifying one or more document types that an authorized user is authorized to sign; and

a signing system in communication with the database and operable to;

receive a signature request from a requester, the signature request requesting that a document be signed;

determine whether the requester is an authorized user authorized to sign the document according to the one or more signing policies; and

sign the document with an organization digital signature generated using an organization private key associated with the organization, if the requestor is an authorized user authorized to sign the document.

49. The system of claim 48, the signing system further operable to:

access the one or more signing policies of the organization by;

accessing the one or more signing policies, the one or more signing policies identifying the one or more document types that an authorized user is authorized to sign by specifying one or more attributes of the one or more document types that the authorized user is authorized to sign; and

determine whether the requester is an authorized user authorized to sign the document according to the one or more signing policies by;

establishing one or more attributes of the document; and

determining whether the one or more attributes of the document match the one or more attributes of the one or more document types that the authorized user is authorized to sign.

50. The system of claim 48, the signing system further operable to receive he signature request from the requester by:

receiving the signature request, the signature request signed with a requestor digital signature generated using a requester private key; and

verifying the signature request using a requestor public key corresponding to the requestor private key.

51. The system of claim 48, the signing system further operable to:

sign the signed document with a sender digital signature generated using a sender private key, the signed document operable to be verified with a sender public key corresponding to the sender private key.

52. The system of claim 48, wherein the signed document is operable to be verified using an organization public key corresponding to the organization private key.

53. The system of claim 48, wherein the organization private key is operable to be authenticated by a certificate authority.

54. The system of claim 48, the signing system further operable to:

send the signed document to a recipient, the recipient distinct from the plurality of authorized users.

55. The system of claim 48, wherein:

the organization comprises a company; and

the plurality of authorized users comprise a plurality of employees of the company.

56. Software for digitally signing a document with a digital signature, the software embodied in a computer-readable medium and operable to:

receive a signature request from a requester, the signature request requesting that a document be signed;

access one or more signing policies of an organization, the one or more signing policies identifying a plurality of authorized users of the organization, the one or more signing policies identifying one or more document types that an authorized user is authorized to sign;

determine whether the requestor is an authorized user authorized to sign the document according to the one or more signing policies; and

sign the document with an organization digital signature generated using an organization private key associated with the organization, if the requestor is an authorized user authorized to sign the document.

57. The software of claim 56, further operable to:

access the one or more signing policies of the organization by;

accessing the one or more signing policies, the one or more signing policies identifying the one or more document types that an authorized user is authorized to sign by specifying one or more attributes of the one or more document types that the authorized user is authorized to sign; and

determine whether the requestor is an authorized user authorized to sign the document according to the one or more signing policies by;

establishing one or more attributes of the document; and

determining whether the one or more attributes of the document match the one or more attributes of the one or more document types that the authorized user is authorized to sign.

58. The software of claim 56, further operable to receive the signature request from the requestor by:

receiving the signature request, the signature request signed with a requestor digital signature generated using a requestor private key; and

verifying the signature request using a requestor public key corresponding to the requester private key.

59. The software of claim 56, further operable to:

sign the signed document with a sender digital signature generated using a sender private key, the signed document operable to be verified with a sender public key corresponding to the sender private key.

60. The software of claim 56, wherein the signed document is operable to be verified using an organization public key corresponding to the organization private key.

61. The software of claim 56, wherein the organization private key is operable to be authenticated by a certificate authority.

62. The software of claim 56, further operable to:

send the signed document to a recipient, the recipient distinct from the plurality of authorized users.

63. The software of claim 56, wherein:

the organization comprises a company; and

the plurality of authorized users comprise a plurality of employees of the company.

64. A system for digitally signing a document with a digital signature, comprising:

means for receiving a signature request from a requestor, the signature request requesting that a document be signed;

means for accessing one or more signing policies of an organization, the one or more signing policies identifying a plurality of authorized users of the organization, the one or more signing policies identifying one or more document types that an authorized user is authorized to sign;

means for determining whether the requestor is an authorized user authorized to sign the document according to the one or more signing policies; and

means for signing the document with an organization digital signature generated using an organization private key associated with the organization, if the requester is an authorized user authorized to sign the document.

65. A method of digitally signing a document with a digital signature, comprising:

receiving a signature request from a requester, the signature request requesting that a document be signed, receiving the signature request from the requester further comprising;

receiving the signature request, the signature request signed with a requester digital signature generated using a requestor private key; and

verifying the signature request using a requestor public key corresponding to the requestor private key;

accessing one or more signing policies of an organization, the organization comprising a company, the one or more signing policies identifying a plurality of authorized users of the organization, the plurality of authorized users comprising a plurality of employees of the company, the one or more signing policies identifying one or more document types that an authorized user is authorized to sign, the one or more signing policies identifying the one or more document types that an authorized user is authorized to sign by specifying one or more attributes of the one or more document types that the authorized user is authorized to sign;

determining whether the requester is an authorized user authorized to sign the document according to the one or more signing policies by;

establishing one or more attributes of the document; and

determining whether the one or more attributes of the document match the one or more attributes of the one or more document types that the authorized user is authorized to sign;

signing the document with an organization digital signature generated using an organization private key associated with the organization, if the requester is an authorized user authorized to sign the document, the signed document operable to be verified using an organization public key corresponding to the organization private key, the organization private key operable to be authenticated by a certificate authority;

signing the signed document with a sender digital signature generated using a sender private key, the signed document operable to be verified with a sender public key corresponding to the sender private key; and

sending the signed document to a recipient, the recipient distinct from the plurality of authorized users.