Systems and methods for subscribing topics and registering computer server event notifications

1. A computer-implemented method of secure transmission of computer server event notifications, the method comprising:

receiving, by a notification server, a topic subscription request from a partner system;

registering, by the notification server, the topic subscription request in a database;

publishing, by the notification server, application programming interfaces (APIs) for secure transmission associated with one or more computer server event notifications, the APIs published by the notification server corresponding to APIs published by a service gateway;

determining, by the notification server, a subscribed partner system subscribed to computer server events of a same type as one or more new computer server events;

generating, by the notification server, a secure event notification associated with the one or more new computer server events;

transmitting, by the notification server, the secure event notification to the subscribed partner system via the APIs published by the notification server and the APIs published by the service gateway; and

registering, by the notification server, the secure event notification in the database.

2. The method of claim 1 , the method further comprising:

obtaining, by the notification server, a plurality of new computer server events to report,

wherein a number of new computer server events among the plurality of new computer server events are combined into a single event notification.

3. The method of claim 1 , wherein generating, by the notification server, the secure event notification further comprises:

signing, by the notification server, the secure event notification with a token payload.

4. The method of claim 3 , wherein the token payload is generated by formatting a header string and a payload string, wherein the header string indicates a type of a token and a type of a hashing algorithm, and wherein the payload string comprises claims information.

5. The method of claim 1 , further comprising:

receiving, by the notification server, an acknowledgment of the transmitted secure event notification from the subscribed partner system; and

setting, by the notification server, a status of the new computer server event as completed.

6. The method of claim 5 , the method further comprising:

retransmitting, by the notification server, the secure event notification to the subscribed partner system when the acknowledgment is not received from the subscribed partner system; and

setting, by the notification server, the status of the new computer server event as failed when a number of failed transmissions of the secure event notification to the subscribed partner system exceeds a predetermined threshold.

7. The method of claim 1 , wherein the secure event notification is generated by:

obtaining, by the notification server, a shared message authentication code (MAC) key associated with the subscribed partner system from a key store;

decrypting, by the notification server, the shared MAC key using a decryption key; and

signing an event notification associated with the new computer server event using the decrypted shared MAC key and a JSON Web Token (JWT).

8. A notification system for secure transmission of computer server event notifications, the system comprising:

a memory having processor-readable instructions stored therein; and

a processor configured to access the memory and execute the processor-readable instructions, which when executed by the processor configure the processor to perform a plurality of functions, including functions to:

receive a topic subscription request from a partner system;

register the topic subscription request in a database;

publish application programming interfaces (APIs) for secure transmission associated with one or more computer server event notifications, the APIs published by the notification server corresponding to APIs published by a service gateway;

determine a subscribed partner system subscribed to computer server events of a same type as one or more new computer server events;

generate a secure event notification associated with the one or more new computer server events;

transmit the secure event notification to the subscribed partner system via the APIs published by the notification server and the APIs published by the service gateway; and

register the secure event notification in the database.

9. The system of claim 8 , wherein the plurality of functions performed by the processor when executing the processor-readable instructions further includes functions to:

obtain a plurality of new computer server events to report,

wherein a number of new computer server events among the plurality of new computer server events are combined into a single event notification.

10. The system of claim 8 , wherein generating the secure event notification further comprises:

signing the secure event notification with a token payload.

11. The system of claim 10 , wherein the token payload is generated by formatting a header string and a payload string, wherein the header string indicates a type of a token and a type of a hashing algorithm, and wherein the payload string comprises claims information.

12. The system of claim 8 , wherein the plurality of functions performed by the processor when executing the processor-readable instructions further includes functions to:

receive an acknowledgment of the transmitted secure event notification from the subscribed partner system; and

set a status of the new computer server event as completed.

13. The system of claim 12 , wherein the plurality of functions performed by the processor when executing the processor-readable instructions further includes functions to:

retransmit the secure event notification to the subscribed partner system when the acknowledgment is not received from the subscribed partner system; and

set the status of the new computer server event as failed when a number of failed transmissions of the secure event notification to the subscribed partner system exceeds a predetermined threshold.

14. The system of claim 8 , wherein the secure event notification is generated by:

obtaining, by the notification server, a shared message authentication code (MAC) key associated with the subscribed partner system from a key store;

decrypting, by the notification server, the shared MAC key using a decryption key; and

signing an event notification associated with the new computer server event using the decrypted shared MAC key and a JSON Web Token (JWT).

15. 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:

receiving, by a notification server, a topic subscription request from a partner system;

registering, by the notification server, the topic subscription request in a database;

publishing, by the notification server, application programming interfaces (APIs) for secure transmission associated with one or more computer server event notifications, the APIs published by the notification server corresponding to APIs published by a service gateway;

determining, by the notification server, a subscribed partner system subscribed to computer server events of a same type as one or more new computer server events;

generating, by the notification server, a secure event notification associated with the one or more new computer server events;

transmitting, by the notification server, the secure event notification to the subscribed partner system via the APIs published by the notification server and the APIs published by the service gateway; and

registering, by the notification server, the secure event notification in the database.

16. The non-transitory computer readable medium of claim 15 , the method further comprising:

obtaining, by the notification server, a plurality of new computer server events to report,

wherein a number of new computer server events among the plurality of new computer server events are combined into a single event notification.

17. The non-transitory computer readable medium of claim 15 , wherein generating, by the notification server, the secure event notification further comprises:

signing, by the notification server, the secure event notification with a token payload.

18. The non-transitory computer readable medium of claim 15 , the method further comprising:

receiving, by the notification server, an acknowledgment of the transmitted secure event notification from the subscribed partner system; and

setting, by the notification server, a status of the new computer server event as completed.

19. The non-transitory computer readable medium of claim 18 , the method further comprising:

retransmitting, by the notification server, the secure event notification to the subscribed partner system when the acknowledgment is not received from the subscribed partner system; and

setting, by the notification server, the status of the new computer server event as failed when a number of failed transmissions of the secure event notification to the subscribed partner system exceeds a predetermined threshold.

20. The non-transitory computer readable medium of claim 15 , wherein the secure event notification is generated by:

obtaining, by the notification server, a shared message authentication code (MAC) key associated with the subscribed partner system from a key store;

decrypting, by the notification server, the shared MAC key using a decryption key; and

signing an event notification associated with the new computer server event using the decrypted shared MAC key and a JSON Web Token (JWT).