Electronic message system with federation of trusted senders
First Claim
1. A computer-implemented method, the method comprising:
- a first authorized server, which includes one or more processors, generating an electronic challenge message, wherein the electronic challenge message;
identifies a sender and a recipient and contains data to be delivered to the recipient; and
includes a federated token identifying that the electronic challenge message was sent from a federated server, the federated token also being configured to be authenticated and validated by a second authorized server that has previously formed a federated relationship with the first authorized server, such that the second authorized server delivers the electronic challenge message to the recipient'"'"'s inbox without the second authorized server generating a second electronic challenge message based at least in part on the electronic challenge message having been sent from a federated server.
6 Assignments
0 Petitions
Accused Products
Abstract
Systems and methods for allowing challenge messages to be sent directly to a recipient'"'"'s inbox where normally the challenge message would be sent to a pending folder or deleted. Challenge messages sent between federated messaging services contain a federated token which can be identified, authenticated and validated to determine whether the challenge message should be sent to a recipient'"'"'s inbox. The federated token can include an authentication portion and a validation portion. Authentication methods for the authentication portion can include, for example, checksums, salts, hashes and digital signatures. Once a federated token is authenticated by decrypting the authentication portion according to one or more of these authentication methods, the federated token is validated by determining the defined use-base and determining whether the receipt of the federated token satisfies the defined use.
178 Citations
20 Claims
-
1. A computer-implemented method, the method comprising:
a first authorized server, which includes one or more processors, generating an electronic challenge message, wherein the electronic challenge message; identifies a sender and a recipient and contains data to be delivered to the recipient; and includes a federated token identifying that the electronic challenge message was sent from a federated server, the federated token also being configured to be authenticated and validated by a second authorized server that has previously formed a federated relationship with the first authorized server, such that the second authorized server delivers the electronic challenge message to the recipient'"'"'s inbox without the second authorized server generating a second electronic challenge message based at least in part on the electronic challenge message having been sent from a federated server. - View Dependent Claims (2, 3, 4, 5)
-
6. One or more non-transitory computer storage media that store an authorization module and a tokenization module, wherein:
-
the authorization module comprises computer-executable instructions that are executable by one or more processors to; receive a first challenge message from a second server, wherein the first challenge message; identifies a first user associated with a first server as a recipient of the first challenge message and a second user associated with the second server as a sender of the first challenge message and contains data to be delivered to the first user; and includes a first federated token identifying the second server; and determine at least one of whether the first federated token is authentic and whether the first federated token is valid; and the tokenization module comprises computer-executable instructions that are executable by the one or more processors to generate a second challenge message identifying a third user associated with the second server as a recipient of the second challenge message and a fourth user associated with the first server as a sender of the second challenge message, the second challenge message comprising; a second federated token that identifies the second challenge message as being sent by a server that previously formed a federated relationship with the second server and that is configured to be one or both of authenticated or validated by the second server and used to deliver the second challenge message to an inbox of the third user without the second server generating a third challenge message in response to receiving the second challenge message based at least in part on the second challenge message having been sent from a federated server. - View Dependent Claims (7, 8, 9, 10, 11, 12, 13, 14)
-
-
15. An authorized server computer system, the authorized server comprising:
-
a processor that is configured to execute computer-executable instructions; computer-executable instructions that are executable by the authorized server to transmit an original message generated by a first user associated with the authorized server to a second server, the original message indicating a second user associated with the second server to receive the original message; an authorization module comprising computer-executable instructions that are executable by the authorized server to; receive a first challenge message from the second server, wherein the first challenge message was generated in response to the first user being unknown to the second user, wherein the first challenge message; identifies the first user as a recipient of the first challenge message and the second user as a sender of the first challenge message and contains data to be delivered to the first user; and includes a first federated token identifying the second server; determine at least one of whether the first federated token is authentic and whether the first federated token is valid; and deliver the first challenge message to an inbox of the first sender when the first challenge message is at least one of authentic and valid; and a tokenization module comprising computer-executable instructions that are executable by the authorized server to generate a second challenge message identifying a third user associated with the second server as a recipient of the second challenge message and a fourth user associated with the first server as a sender of the second challenge message, the second challenge message comprising; a second federated token that identifies the second challenge message as being sent by a server that previously formed a federated relationship with the second server and that is configured to be one or both of authenticated or validated by the second server and used to deliver the second challenge message to an inbox of the third user without the second server generating a third challenge message in response to receiving the second challenge message based at least in part on the second challenge message having been sent from a federated server. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification