Secure message routing in multi tenant system without content inspection
AssigneeYokogawa Electric Corporation
InventorJeff Melrose
Life of this patent
Estimating the term…
Abstract
A method for message routing in a multi-tenant system includes encrypting an ID of a tenant with a public key that is generated for the tenant together with a corresponding private key; storing a set of the encrypted ID and the public key in both a device and a server of the multi-tenant system; transmitting from the device to the server a message comprising the set of the encrypted ID and the public key stored in the device; and detecting whether the message is directed toward a data store for the tenant by comparing the set comprised in the message and the set stored in the server.
Claims10
A method for message routing in a multi-tenant system, comprising:
- encrypting an ID of a tenant with a public key that is generated for the tenant together with a corresponding private key;
- storing a set of the encrypted ID and the public key in both a device and a server of the multi-tenant system;
- transmitting from the device to the server a message comprising the set of the encrypted ID and the public key stored in the device;
- and
- detecting whether the message is directed toward a data store for the tenant by comparing the set comprised in the message and the set stored in the server.
A system comprising:
- a server that comprises a data store;
- a first device that transmits a message to the server;
- and
- a second device that:
- encrypts an ID of a tenant with a public key that is generated for the tenant together with a corresponding private key;
- and
- stores a set of the encrypted ID and the public key in both the server and the first device,
- wherein the first device transmits to the server the message comprising the set of the encrypted ID and the public key;
- and
- the server detects whether the message is directed toward the data store for the tenant by comparing the set comprised in the message and the set stored in the server.
Dependencies are inferred from the claim text.