Secure federation of data communications networks

• US 20050265327A1
• Filed: 05/27/2004
• Published: 12/01/2005
• Est. Priority Date: 05/27/2004
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kimchi, Gur, Shoroff, Srikanth, Buch, Jeremy
• Granted Patent: US 7,506,369 B2
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources

Abstract

Techniques for secure federation of data communications networks are provided. The techniques employ an edge proxy server to route messages depending on a federation mode. In Direct federation mode, an edge proxy server of a network is configured to exchange messages with a specified set of entities, such as other networks, servers, other devices, or users. In Automatic federation mode, an edge proxy server may accept all incoming messages from entities that have a valid certificate. In Clearinghouse federation mode, the edge proxy server forwards all outgoing messages to a specified, trusted clearinghouse server.

Claims

1. A method performed by an edge proxy server for federating a network in a direct federation mode, comprising:

receiving an indication of authorized entities;

receiving a message;

verifying that the message was sent by an authorized and authenticated entity; and

after verifying that the message was sent by an authorized and authenticated entity,

determining a next hop for the message; and

forwarding the message to the next hop.

2. The method of claim 1 wherein the message is received using a session initiation protocol.

3. The method of claim 1 wherein the indication of authorized entities is a list.

4. The method of claim 3 wherein the list comprises entities designated by an administrator to be authorized.

5. The method of claim 3 wherein an entity is authorized when it does not appear on the list.

6. The method of claim 1 wherein the next hop is determined from a header field of the message.

7. The method of claim 1 wherein the next hop is determined by querying a server.

8. The method of claim 7 wherein the server is a domain name service.

9. The method of claim 1 wherein the next hop is determined from a list of authorized entities.

10. A method performed by an edge proxy server for federating a network in an automatic federation mode, comprising:

receiving a message;

verifying that the message was sent by an authenticated entity;

determining whether a certificate indicated in a header field of the received message appears in a list of revoked certificates; and

when the received message is an incoming message,

verifying that a uniform resource identifier indicated for a sender of the message matches a domain from which the message was received; and

when the received message is an outgoing message, querying a domain name service.

11. The method of claim 10 wherein the querying includes determining a next hop for the message.

12. A method performed by an edge proxy server for federating a network in a clearinghouse federation mode, comprising:

receiving a message;

forwarding the received message to a recipient specified in the message; and

establishing a session directly between a sender of the received message and a recipient of the received message.

13. The method of claim 12 including verifying that the message was received on a valid connection.

14. The method of claim 12 wherein a header field of the received message includes a certificate.

15. An edge proxy server system for federating a network, comprising:

a component that receives an indication of a federation mode for the proxy server;

a component that receives a message;

a component that authenticates a sender of the received message based on the indicated federation mode; and

a component that handles the message based on the indicated federation mode and whether the sender of the received message is authenticated.

16. The system of claim 15 wherein the handling includes forwarding the message when a recipient indicated in the message does not appear in a deny list.

17. The system of claim 15 wherein the federation mode is direct.

18. The system of claim 17 wherein a sender is authenticated by determining whether the sender sent the message in a valid connection.

19. The system of claim 17 wherein the handling includes forwarding the message when a recipient indicated in the message appears in an accept list.

20. The system of claim 17 wherein the handling includes determining a next hop for the message.

21. The system of claim 15 wherein the federation mode is automatic.

22. The system of claim 21 wherein the sender is authenticated when the message was sent in a valid connection.

23. The system of claim 21 wherein the sender is authenticated when a domain of a URI indicated for the sender matches a domain of an entity that actually sent the message.

24. The system of claim 21 wherein the handling includes determining services offered by a destination entity indicated in the message.

25. The system of claim 24 wherein a service is mutually authenticated transport layer security.

26. The system of claim 15 wherein the federation mode is clearinghouse.

27. The system of claim 26 wherein the handling includes receiving messages from the clearinghouse.

28. The system of claim 27 wherein the sender is implicitly trusted.

29. The system of claim 26 wherein the handling includes forwarding outgoing messages to a clearinghouse.

30. The system of claim 26 wherein the handling includes establishing a session directly with the sender.

31. The system of claim 15 wherein the federation mode includes a combination of federation modes.

32. The system of claim 31 wherein the combination of federation modes includes a direct federation mode, an automatic federation mode, and a clearinghouse federation mode.

33. The system of claim 31 wherein the authentication includes receiving a certificate.

34. A computer-readable medium having computer-executable instructions for performing steps, comprising:

receiving an indication of authorized entities;

receiving a message;

determining whether an entity that sent the message is authorized; and

when the entity that sent the message is authorized,

authenticating the authorized entity, wherein the authenticating includes determining whether the message was received on a valid connection; and

when the authorized entity is authenticated,

determining a next hop for the message; and

forwarding the message to the next hop.

35. The computer-readable medium of claim 34 including instructions for performing steps relating to determining whether the message was received from the authorized entity in a valid connection.

36. An edge proxy server for federating a network, comprising:

means for establishing sessions with computing devices;

means for authorizing the computing devices;

means for validating messages from or to the computing devices;

means for determining a destination for the validated messages;

means for routing the messages to the determined destination.

37. The edge proxy server of claim 36 wherein the means for establishing sessions with computing devices controls a number of sessions.

38. The edge proxy server of claim 36 wherein the means for authorizing computing devices may have an associated list of unauthorized entities.

39. The edge proxy server of claim 36 wherein the means for validating messages validates messages based on contents of the messages.

40. The edge proxy server of claim 36 wherein the means for routing messages routes messages depending on a federation mode.