Systems and methods for registering computer server event notifications
A system for secure transmission of business event notifications includes a memory, at least one processor, a service gateway configured to: publish application programming interfaces (APIs) for secure transmission of business event notifications, a notification server configured to: publish APIs for secure transmission of business event notifications corresponding to the APIs published by the service gateway, obtain a new business event to report, determine a partner to receive a notification of the new business event, transmit an event notification to the partner by way of the service gateway APIs, and register the event notification in a database.
1. A method of secure transmission of computer server event notifications, the method comprising:
publishing application programming interfaces (APIs) for secure transmission of computer server event notifications over a computer network, the APIs corresponding to APIs published by a service gateway;
obtaining a new computer server event to report;
determining a subscribed partner system subscribed to the new computer server event;
generating a token payload based on a header string and a payload string associated with the new computer server event to report;
generating a token signature based on the token payload and a shared key associated with the subscribed partner system;
generating a notification payload based on the header string, the payload string, and the token signature; and
transmitting the notification payload to the subscribed partner system over the computer network by way of the APIs published by the service gateway.
2. The method of claim 1 , wherein the APIs published by the service gateway include features for secure transmission of event notifications.
3. The method of claim 2 , wherein the features for secure transmission of event notifications include one or more of message authentication codes (MAC), JavaScript Object Notation (JSON) Web Tokens (JWT), and Hypertext Transfer Protocol Secure (HTTPS).
4. The method of claim 1 , wherein the APIs published by the service gateway include interfaces for receiving computer server events from external services.
5. The method of claim 4 , further comprising:
publishing APIs for receiving computer server events from external services, the APIs corresponding to the APIs published by the service gateway; and
receiving the new computer server event from an external service by way of the APIs published by the service gateway.
6. The method of claim 1 , further comprising:
receiving an acknowledgment of the transmitted notification payload from the subscribed partner system; and
setting a status of the new computer server event as completed.
7. The method of claim 6 , further comprising:
retransmitting the notification payload to the subscribed partner system when an acknowledgment is not received from the subscribed partner system; and
setting a status of the new computer server event as failed when a number of failed transmissions of the notification payload to the subscribed partner system exceeds a predetermined threshold.
8. The method of claim 1 , wherein the header string comprises a designation of a type of a token and a designation of a hashing algorithm.
9. The method of claim 1 , further comprising:
retrieving a key from a global key store.
10. The method of claim 9 , wherein the shared key is decrypted using the key prior to generating the token signature.
11. The method of claim 1 , wherein the token signature is a JavaScript Object Notation (JSON) Web Signature (JWS).
12. A computer system for secure transmission of computer server event notifications, the system comprising:
a service gateway configured to:
publish application programming interfaces (APIs) for secure transmission of computer server event notifications over a computer network;
a notification server configured to:
publish APIs for secure transmission of computer server event notifications over the computer network, the APIs corresponding to the APIs published by the service gateway;
obtain a new computer server event to report;
determine a subscribed partner system subscribed to the new computer server event to report;
generate a token payload based on a header string and a payload string associated with the new computer server event to report;
generate a token signature based on the token payload and a shared key associated with the subscribed partner system;
generate a notification payload based on the header string, the payload string, and the token signature; and
transmit the notification payload to the subscribed partner system over the computer network by way of the APIs published by the service gateway.
13. The system of claim 12 , wherein the notification server is further configured to:
receive an acknowledgment of the transmitted notification payload from the subscribed partner system; and
set a status of the new computer server event as completed.
14. The system of claim 13 , wherein the notification server is further configured to:
retransmit the notification payload to the subscribed partner system when an acknowledgment is not received from the subscribed partner system; and
set a status of the new computer server event as failed when a number of failed transmissions of the notification payload to the subscribed partner system exceeds a predetermined threshold.
15. The system of claim 12 , wherein the notification server is further configured to:
retrieve a key from a global key store.
16. The system of claim 15 , wherein the shared key is decrypted using the key prior to generating the token signature.
17. A non-transitory computer readable medium storing a program causing a computer to execute a method of secure transmission of computer server event notifications, the method comprising:
publishing application programming interfaces (APIs) for secure transmission of computer server event notifications over a computer network, the APIs corresponding to APIs published by a service gateway;
obtaining a new computer server event to report;
determining a subscribed partner system subscribed to the new computer server event;
generating a token payload based on a header string and a payload string associated with the new computer server event to report;
generating a token signature based on the token payload and a shared key associated with the subscribed partner system;
generating a notification payload based on the header string, the payload string, and the token signature; and
transmitting the notification payload to the subscribed partner system over the computer network by way of the APIs published by the service gateway.
18. The non-transitory computer readable medium of claim 17 , wherein the APIs published by the service gateway include features for secure transmission of event notifications.
19. The non-transitory computer readable medium of claim 18 , wherein the features for secure transmission of event notifications include one or more of message authentication codes (MAC), JavaScript Object Notation (JSON) Web Tokens (JWT), and Hypertext Transfer Protocol Secure (HTTPS).
20. The non-transitory computer readable medium of claim 17 , wherein the APIs published by the service gateway include interfaces for receiving computer server events from external services.