Traffic manager for distributed computing environments
View Patent ↗Techniques suitable for facilitating communications between various computer programs operating on various nodes in a distributed computing environment are disclosed. The techniques can be used by a traffic manager operating in such environments. The traffic manager is capable of monitoring traffic exchanged between client and server programs operating in the distributed computing environment. Moreover, the traffic manager can be used to implement a variety of desirable features across different computing environments. These computing environments are typically separated by one or more distinguishing characteristics. As will be appreciated, the traffic manager provides an integral and cost effective solution which can bridge these distinguishing characteristics as well as define and enforce policies across disparate computing environments. This is achieved by centralizing the generation of interfaces which allow interaction between any of the nodes in a distributed computing system. This avoids the redundancy and inefficiency inherent in building these capabilities in each node, particularly in complex systems.
1. A computer-implemented method of implementing security for Simple Object Access Protocol (SOAP) messages which can be exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one security rule has been defined for the SOAP message, the at least one security rule being defined based on a security policy for exchanging SOAP messages between at least one client program and at least one server program, wherein the at least one security rule includes at least one decryption rule; and
performing at least one security related operation on the SOAP message based on the at least one security rule when the determining determines that at least one security rule is associated with the SOAP message, wherein the performing of the at least one operation comprises:
determining whether the SOAP message is encrypted, and
decrypting the SOAP message based on one or more decryption keys which are associated with the at least one decryption rule.
2. A method as recited in claim 1 , wherein the one or more decryption keys are managed by an organization or define an organizational rule.
3. A method as recited in claim 1 , wherein the method further comprises:
determining whether the SOAP message has been decrypted successfully; and
taking appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
4. A computer-implemented method of implementing security for Simple Object Access Protocol (SOAP) messages which can be exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one security rule has been defined for the SOAP message, he at least one security rule being defined based on a security policy for exchanging SOAP messages between at least one client program and at least one server program, wherein the at least one security rule includes at least one encryption rule; and
performing at least one security related operation on the SOAP message based on the at least one security rule when the determining determines that at least one security rule is associated with the SOAP message, wherein the performing of at least one operation comprises:
encrypting the SOAP message based on one or more encryption keys which are associated with the at least one encryption rule.
5. A method as recited in claim 4 , wherein the one or more encryption keys are associated with an individual.
6. A computer-implemented method of implementing security for Simple Object Access Protocol (SOAP) messages exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one decryption rule is associated with the SOAP message;
attempting to decrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one decryption rule is associated with the SOAP message;
determining whether at least one encryption rule is associated with the SOAP message;
encrypting the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one encryption rule is associated with the SOAP message;
determining whether at least one signature verification rule is associated with the SOAP message;
verifying at least one signature associated with the SOAP message per requirements specified by the at least one signature verification rule when the determining determines that at least one signature verification rule is associated with the SOAP message;
determining whether at least one signing rule is associated with the SOAP message; and
signing the SOAP message using one or more keys associated with the at least one signing rule.
7. A method as recited in claim 6 , wherein the method further comprises:
determining a message type for the SOAP message, and
looking up rules which are associated with the message type.
8. A method as recited in claim 6 , wherein at least one portion of the SOAP message is XML.
9. A method as recited in claim 6 , wherein the method further comprises:
determining whether the SOAP message is encrypted before attempting to decrypt the SOAP message;
determining whether the SOAP message has been decrypted successfully; and
taking appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
10. A method as recited in claim 6 , wherein the method further comprises:
determining whether the at least one signature associated with the SOAP message has successfully been verified; and
taking appropriate action when the determining determines that the at least one signature has not been successfully verified.
11. A computer readable medium having computer program instructions stored therein for performing a method of implementing security for Simple Object Access Protocol (SOAP) messages exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one decryption rule is associated with the SOAP message;
attempting to decrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one decryption rule is associated with the SOAP message;
determining whether at least one encryption rule is associated with the SOAP message;
encrypting the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one encryption rule is associated with the SOAP message;
determining whether at least one signature verification rule is associated with the SOAP message;
verifying at least one signature associated with the SOAP message per requirements specified by the at least one signature verification rule when the determining determines that at least one signature verification rule is associated with the SOAP message;
determining whether at least one signing rule is associated with the SOAP message; and
signing the SOAP message using one or more keys associated with the at least one signing rule.
12. The computer readable medium of claim 11 , wherein the method further comprises:
determining a message type for the SOAP message, and
looking up rules which are associated with the message type.
13. The computer readable medium of claim 11 , wherein at least one portion of the SOAP message is XML.
14. The computer readable medium of claim 11 , wherein the method further comprises:
determining whether the SOAP message is encrypted before attempting to decrypt the SOAP message;
determining whether the SOAP message has been decrypted successfully; and
taking appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
15. The computer readable medium of claim 11 , wherein the method further comprises:
determining whether the at least one signature associated with the SOAP message has successfully been verified; and
taking appropriate action when the determining determines that the at least one signature has not been successfully verified.
16. A traffic manager for facilitating communication between a client node and a server node in a distributed computing environment, the server node having a first interface associated therewith which is incompatible with direct communications generated by the client node, the traffic manager comprising a central processing unit which can operate to:
receive a Simple Object Access Protocol (SOAP) message;
determine whether at least one decryption rule is associated with the SOAP message;
attempt to decrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one decryption rule is associated with the SOAP message;
determine whether at least one encryption rule is associated with the SOAP message;
encrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one encryption rule is associated with the SOAP message;
determine whether at least one signature verification rule is associated with the SOAP message;
verify at least one signature associated with the SOAP message per requirements specified by the at least one signature verification rule when the determining determines that at least one signature verification rule is associated with the SOAP message;
determine whether at least one signing rule is associated with the SOAP message; and
sign the SOAP message using one or more keys associated with the at least one signing rule.
17. The traffic manager of claim 16 , wherein the central processing unit can further operate to:
determine a message type for the SOAP message, and
look up rules which are associated with the message type.
18. The traffic manager of claim 16 , wherein at least one portion of the SOAP message is XML.
19. The traffic manager of claim 16 , wherein the central processing unit can further operate to:
determine whether the SOAP message is encrypted before attempting to decrypt the SOAP message;
determine whether the SOAP message has been decrypted successfully; and
take appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
20. The traffic manager of claim 16 , wherein the central processing unit can further operate to:
determine whether the at least one signature associated with the SOAP message has successfully been verified; and
take appropriate action when the determining determines that the at least one signature has not been successfully verified.
21. A computer readable medium having computer program instructions stored therein for performing a method of implementing security for Simple Object Access Protocol (SOAP) messages which can be exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one security rule has been defined for the SOAP message, the at least one security rule being defined based on a security policy for exchanging SOAP messages between at least one client program and at least one server program, wherein the at least one security rule includes at least one decryption rule; and
performing at least one security related operation on the SOAP message based on the at least one security rule when the determining determines that at least one security rule is associated with the SOAP message, wherein the performing of the at least one operation comprises:
determining whether the SOAP message is encrypted, and
decrypting the SOAP message based on one or more decryption keys which are associated with the at least one decryption rule.
22. The computer readable medium of claim 21 , wherein the one or more decryption keys are managed by an organization or define an organizational rule.
23. The computer readable medium of claim 21 , wherein the method further comprises:
determining whether the SOAP message has been decrypted successfully; and
taking appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
24. A traffic manager for facilitating communication between a client node and a server node in a distributed computing environment, the server node having a first interface associated therewith which is incompatible with direct communications generated by the client node, the traffic manager comprising a central processing unit which can operate to:
receive a Simple Object Access Protocol (SOAP) message;
determine whether at least one security rule has been defined for the SOAP message, the at least one security rule being defined based on a security policy for exchanging SOAP messages between at least one client program and at least one server program, wherein the at least one security rule includes at least one decryption rule; and
perform at least one security related operation on the SOAP message based on the at least one security rule when the determining determines that at least one security rule is associated with the SOAP message, wherein the performing of the at least one operation comprises:
determining whether the SOAP message is encrypted, and
decrypting the SOAP message based on one or more decryption keys which are associated with the at least one decryption rule.
25. The traffic manager of claim 24 , wherein the one or more decryption keys are managed by an organization or define an organizational rule.
26. The traffic manager of claim 24 , wherein the central processing unit can further operate to:
determine whether the SOAP message has been decrypted successfully; and
take appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
27. A computer readable medium having computer program instructions stored therein for performing a method of implementing security for Simple Object Access Protocol (SOAP) messages which can be exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one security rule has been defined for the SOAP message, the at least one security rule being defined based on a security policy for exchanging SOAP messages between at least one client program and at least one server program, wherein the at least one security rule includes at least one encryption rule; and
performing at least one security related operation on the SOAP message based on the at least one security rule when the determining determines that at least one security rule is associated with the SOAP message, wherein the performing of at least one operation comprises:
encrypting the SOAP message based on one or more encryption keys which are associated with the at least one encryption rule.
28. The computer readable medium of claim 27 , wherein the one or more encryption keys are associated with an individual.
29. A traffic manager for facilitating communication between a client node and a server node in a distributed computing environment, the server node having a first interface associated therewith which is incompatible with direct communications generated by the client node, the traffic manager comprising a central processing unit which can operate to:
receive a Simple Object Access Protocol (SOAP) message;
determine whether at least one security rule has been defined for the SOAP message, the at least one security rule being defined based on a security policy for exchanging SOAP messages between at least one client program and at least one server program, wherein the at least one security rule includes at least one encryption rule; and
perform at least one security related operation on the SOAP message based on the at least one security rule when the determining determines that at least one security rule is associated with the SOAP message, wherein the performing of at least one operation comprises:
encrypting the SOAP message based on one or more encryption keys which are associated with the at least one encryption rule.
30. The traffic manager of claim 29 , wherein the one or more encryption keys are associated with an individual.
31. A computer-implemented method of implementing security for Simple Object Access Protocol (SOAP) messages exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one decryption rule is associated with the SOAP message;
attempting to decrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one decryption rule is associated with the SOAP message;
determining whether at least one encryption rule is associated with the SOAP message; and
encrypting the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one encryption rule is associated with the SOAP message.
32. A method as recited in claim 31 , wherein the method further comprises:
determining a message type for the SOAP message, and
looking up rules which are associated with the message type.
33. A method as recited in claim 31 , wherein at least one portion of the SOAP message is XML.
34. A method as recited in claim 31 , wherein the method further comprises:
determining whether the SOAP message is encrypted before attempting to decrypt the SOAP message;
determining whether the SOAP message has been decrypted successfully; and
taking appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
35. A method as recited in claim 31 , wherein the method further comprises:
determining whether the at least one signature associated with the SOAP message has successfully been verified; and
taking appropriate action when the determining determines that the at least one signature has not been successfully verified.
36. A computer readable medium having computer program instructions stored therein for performing a method of implementing security for Simple Object Access Protocol (SOAP) messages exchanged between client and server programs, the method comprising:
receiving a SOAP message;
determining whether at least one decryption rule is associated with the SOAP message;
attempting to decrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one decryption rule is associated with the SOAP message;
determining whether at least one encryption rule is associated with the SOAP message; and
encrypting the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one encryption rule is associated with the SOAP message.
37. The computer readable medium of claim 36 , wherein the method further comprises:
determining a message type for the SOAP message, and
looking up rules which are associated with the message type.
38. The computer readable medium of claim 36 , wherein at least one portion of the SOAP message is XML.
39. The computer readable medium of claim 36 , wherein the method further comprises:
determining whether the SOAP message is encrypted before attempting to decrypt the SOAP message;
determining whether the SOAP message has been decrypted successfully; and
taking appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
40. The computer readable medium of claim 36 , wherein the method further comprises:
determining whether the at least one signature associated with the SOAP message has successfully been verified; and
taking appropriate action when the determining determines that the at least one signature has not been successfully verified.
41. A traffic manager for facilitating communication between a client node and a server node in a distributed computing environment, the server node having a first interface associated therewith which is incompatible with direct communications generated by the client node, the traffic manager comprising a central processing unit which can operate to:
receive a Simple Object Access Protocol (SOAP) message;
determine whether at least one decryption rule is associated with the SOAP message;
attempt to decrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one decryption rule is associated with the SOAP message;
determine whether at least one encryption rule is associated with the SOAP message; and
encrypt the SOAP message using one or more keys associated with the at least one decryption rule when the determining determines that at least one encryption rule is associated with the SOAP message.
42. The traffic manager of claim 41 , wherein the central processing unit can further operate to:
determine a message type for the SOAP message, and
look up rules which are associated with the message type.
43. The traffic manager of claim 41 , wherein at least one portion of the SOAP message is XML.
44. The traffic manager of claim 41 , wherein the central processing unit can further operate to:
determine whether the SOAP message is encrypted before attempting to decrypt the SOAP message;
determine whether the SOAP message has been decrypted successfully; and take appropriate action when the determining determines that the SOAP message has not been decrypted successfully.
45. The traffic manager of claim 41 , wherein the central processing unit can further operate to:
determine whether the at least one signature associated with the SOAP message has successfully been verified; and
take appropriate action when the determining determines that the at least one signature has not been successfully verified.