Data Replication Across Enterprise Boundaries

• US 20110161289A1
• Filed: 12/30/2009
• Published: 06/30/2011
• Est. Priority Date: 12/30/2009
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: VeriSign, Inc.
• Inventors: Sun, Ruiping, Hoang, Oanh, Pei, Mingliang, Huang, John
• Granted Patent: US 9,286,369 B2
• Time in Patent Office: Days
• US Class Current: 707/613
• CPC Class Codes: G06F 16/275 Synchronous replication

Abstract

Systems and methods for synchronizing verification data in a distributed database including client and server databases. The server database may exchange verification data regarding one-time passwords to multiple client databases. An update to the server database may be initiated based on information stored in the client database by pushing updated verification information from the client database to the server database via an SSL tunnel. An update to the client database may be initiated based on information stored in the server database by pulling updated verification data from the server database to the client database via an SSL tunnel. The client database and the server database may include a two-dimensional data field including the verification data and an associated key identifier, and a site ID. The site ID may include a unique identifier to identify the respective database in which it is included. The data field may include a sequence number assigned to each row of data that increases every time the row of information is updated. The client database and the server database may also include a replication tracking table including a record of the last known update to a remote database. Data fields that require updating may be determined based on the site ID and a comparison of the sequence numbers from the replication tracking table and the server'"'"'s database.

Claims

1. A method for synchronizing verification data in a distributed database including client and server databases, the server database exchanging verification data to multiple client databases, the method comprising:

performing an update operation by a client server resulting in a change in one row of a table in the client database;

initiating an update to the server database based on information stored in the client database by pushing updated verification information from the client database to the server database via an SSL tunnel;

initiating an update to the client database based on information stored in the server database by pulling updated verification data from the server database to the client database via an SSL tunnel; and

updating the verification data in the client database based on updated information pulled from the server database.

2. The method of claim 1, wherein the server database exchanges verification data regarding one-time passwords to the multiple client databases, the method further comprising:

receiving a user token identifier and a one-time password at the client server;

validating the one-time password at the client server based on verification data stored in the client database, the verification data associated with the user token identifier;

providing a validation response from the client server based on the validating of the one-time password;

updating the verification data in the client database based on the validation response; and

updating the verification data regarding the token identifier in the client database based on updated information pulled from the server database.

3. The method of claim 1, wherein:

the client database and the server database each comprise;

a two-dimensional data field including the verification data and an associated key identifier;

a site ID, the site ID comprising a unique identifier to identify the respective database in which it is included;

a sequence number assigned to each row of data, the sequence number increasing every time the row of information is updated; and

a replication tracking table comprising a record of the last known update to at least one of the server database and another client database, the record including a site ID and a sequence number; and

data fields that require updating during the pulling are determined based on the site ID and a comparison of the sequence number in the server database and at least one of the client databases, a data field determined to have been changed when it has a larger sequence number than that of data in another database with the same site ID.

4. The method of claim 1, wherein:

the server database and client database are independently updated during an inter-update period between the server database and client database;

at least one of the server database and client database resolve which update information to apply from the independent updates based on at least one of unique data within the updated information, timestamp data within the updated information; and

an authority assigned to the database with the updated information.

5. The method of claim 4, wherein at least one of the server database and client database resolve which update information to apply based on the unique data within the updated information.

6. The method of claim 4, wherein at least one of the server database and client database resolve which update information to apply based on the timestamp data within the updated information.

7. The method of claim 4, wherein at least one of the server database and client database resolve which update information to apply based on the authority assigned to the database with the updated information.

8. The method of claim 4, wherein:

the client server comprises a plurality of client servers, each client server maintaining a respective client database; and

different verification data conflict resolution rules are set by different client servers.

9. The method of claim 4, wherein validating for a single user token identifier by various client servers proceeds asynchronously with respect to the updating.

23. The method of claim 1, further comprising:

comparing a sequence number associated with updated information from a client database to another sequence number associated with stored information in at least one of another client database or the server database; and

if the numbers match, reporting a replay attack associated with the key identifier for the updated information.

10. A method for synchronizing verification data in a distributed database including client and server databases, the server database exchanging verification data to multiple client databases, the method comprising:

receiving a request to update a server database from a first client database by pushing updated verification data from the first client database to the server database via an SSL tunnel;

updating verification data stored in the server database based on the updated verification data from the first client database;

receiving a request to update at least one of the first client database and a second client database based on information stored in the server database by pulling updated verification data from the server database to the at least one of first client database and second client database via an SSL tunnel;

sending updated verification information to the at least one of first client database and second client database requesting the updated verification information from the server database.

11. The method of claim 10, wherein the verification data relates to one-time passwords that are automatically verified by at least one of the client and server.

12. The method of claim 10, wherein:

the client database and the server database each comprise;

a two-dimensional data field including the verification data and an associated key identifier;

a site ID, the site ID comprising a unique identifier to identify the respective database in which it is included; and

a sequence number assigned to each row of data, the sequence number increasing every time the row of information is updated; and

a replication tracking table comprising a record of the last known update to at least one of the server database and another client database, the record including a site ID and a sequence number; and

data fields that require updating are determined based on the site ID and a comparison of the sequence number in the server database and at least one of the client databases, a data field determined to have been changed when it has a larger sequence number than that of data in another database with the same site ID.

13. The method of claim 10, wherein:

the server database and client database are independently updated during an inter-update period between the server database and client database;

at least one of the server database and client database resolve which update information to apply based on at least one of unique data within the updated information, timestamp data within the updated information; and

an authority assigned to the database with the updated information.

14. The method of claim 13, wherein at least one of the server database and client database resolve which update information to apply based on the unique data within the updated information.

15. The method of claim 13, wherein at least one of the server database and client database resolve which update information to apply based on the timestamp data within the updated information.

16. The method of claim 13, wherein at least one of the server database and client database resolve which update information to apply based on the authority assigned to the database with the updated information.

17. The method of claim 13, wherein:

the client server comprises a plurality of client servers, each client server maintaining a respective client database; and

different verification data conflict resolution rules are set by different client servers.

24. The method of claim 11, further comprising:

comparing a sequence number associated with updated information from a client database to another sequence number associated with stored information in at least one of another client database or the server database; and

if the numbers match, reporting a replay attack associated with the key identifier for the updated information.

18. A method for synchronizing data in a distributed database including client and server databases, the server database exchanging data to multiple client databases, the method comprising:

performing an update operation by a client server resulting in a change in one row of a table in the client database;

initiating an update to the server database from the client database by pushing updated verification information from the client database to the server database;

initiating an update to the client database from the server database by pulling updated verification information from the server database to the client database; and

updating the verification information regarding the identifier in the client database based on updated information pulled from the server database.

19. The method of claim 18, wherein the server database exchanges verification data regarding one-time passwords to the multiple client databases, the method further comprising:

receiving an identifier and a one-time password at a client server;

validating the one-time password at the client server based on verification data stored in a client database, the verification data associated with the identifier;

providing a validation response from the client server based on the validating of the one-time password; and

updating the verification data in the client database based on the validation response.

20. The method of claim 18, wherein the updating are conducted over an SSL tunnel between the server and client database.

21. The method of claim 18, wherein the updating are initiated only by requests from the client and conducted over an SSL tunnel between the server and client database formed in response to the requests.

22. The method of claim 18, wherein:

the client database and the server database each comprise;

a two-dimensional data field including the verification data and an associated key identifier;

a site ID, the site ID comprising a unique identifier to identify the respective database in which the site ID is included; and

a sequence number assigned to each row of data, the sequence number increasing every time the row of information is updated; and

a replication tracking table comprising a record of the last known update to at least one of the server database and another client database, the record including a site ID and a sequence number; and

data fields that require updating are determined based on the site ID and a comparison of the sequence number in the server database and at least one of the client databases, a data field determined to have been changed when it has a larger sequence number than that of data in another database with the same site ID.

25. The method of claim 20, further comprising:

comparing a sequence number associated with updated information from a client database to another sequence number associated with stored information in at least one of another client database or the server database; and

if the numbers match, reporting a replay attack associated with the key identifier for the updated information.