A system comprising: a client computing device that is executing a client-side instance of a unified communications application; a first server that is executing a first server-side instance of the unified communications application; and a second server that is executing a second server-side instance of the unified communications application, wherein the client computing device is configured to transmit a first request to the first server; wherein the first server is configured to generate and transmit a web ticket to the client computing device subsequent to receiving the first request, the web ticket comprising a signature that is based upon a first symmetric key shared between the first server and the second server, and a key identifier that identifies the first symmetric key used to generate the web ticket, wherein the client computing device is configured to transmit a second request to the second server subsequent to receiving the web ticket, wherein the second request comprises the web ticket, wherein the second server is configured to extract and validate the signature based upon the key identifier, and wherein the client computing device is configured to receive a data packet from the second server based upon the second request, subsequent to the web ticket being validated by the second server; wherein the system is characterized in that: the first server is configured to maintain a queue of multiple symmetric keys, wherein the queue of multiple symmetric keys comprises the first symmetric key that is immediately usable by the first server to generate the web ticket, and a second key that is subsequently usable by the first server to generate the web ticket immediately after the first key expires; and wherein the second server is configured to request the queue of symmetric keys and to use the key identifier to identify, in the queue of symmetric keys, the symmetric key used to generate the web ticket in the received queue of symmetric keys. a client computing device that is executing a client-side instance of a unified communications application; a first server that is executing a first server-side instance of the unified communications application; and a second server that is executing a second server-side instance of the unified communications application, wherein the client computing device is configured to transmit a first request to the first server; wherein the first server is configured to generate and transmit a web ticket to the client computing device subsequent to receiving the first request, the web ticket comprising a signature that is based upon a first symmetric key shared between the first server and the second server, and a key identifier that identifies the first symmetric key used to generate the web ticket, wherein the client computing device is configured to transmit a second request to the second server subsequent to receiving the web ticket, wherein the second request comprises the web ticket, wherein the second server is configured to extract and validate the signature based upon the key identifier, and wherein the client computing device is configured to receive a data packet from the second server based upon the second request, subsequent to the web ticket being validated by the second server; wherein the system is characterized in that: the first server is configured to maintain a queue of multiple symmetric keys, wherein the queue of multiple symmetric keys comprises the first symmetric key that is immediately usable by the first server to generate the web ticket, and a second key that is subsequently usable by the first server to generate the web ticket immediately after the first key expires; and wherein the second server is configured to request the queue of symmetric keys and to use the key identifier to identify, in the queue of symmetric keys, the symmetric key used to generate the web ticket in the received queue of symmetric keys. the first server is configured to maintain a queue of multiple symmetric keys, wherein the queue of multiple symmetric keys comprises the first symmetric key that is immediately usable by the first server to generate the web ticket, and a second key that is subsequently usable by the first server to generate the web ticket immediately after the first key expires; and wherein the second server is configured to request the queue of symmetric keys and to use the key identifier to identify, in the queue of symmetric keys, the symmetric key used to generate the web ticket in the received queue of symmetric keys.