SYSTEMS AND METHODS FOR LOGGING INTO AN APPLICATION ON A SECOND DOMAIN FROM A FIRST DOMAIN IN A MULTI-TENANT DATABASE SYSTEM ENVIRONMENT

• US 20110302631A1
• Filed: 12/30/2010
• Published: 12/08/2011
• Est. Priority Date: 06/07/2010
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Sureshchandra, Jayesh, Luh, Addison
• Granted Patent: US 9,426,142 B2
• Time in Patent Office: Days
• US Class Current: 726/4
• CPC Class Codes: G06F 16/28 Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 21/34 involving the use of external additional devices, e.g. dongles or smart cards
• CPC Class Codes: G06F 21/41 where a single sign-on provides access to a plurality of computers
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations

Abstract

A system and method for logging into an application across separate domains in a multi-tenant database environment is provided. The method may include receiving, by a server associated with a first domain, a substitute user request from a user of the first domain, the substitute user request including a request for the user of the first domain to become a user on a second domain, posting, to a server associated with the second domain, the substitute user request, and posting, by the server associated with the second domain, a new session identification allowing the user of the first domain to login to an application on the second domain.

Claims

1. A method for logging into an application across separate domains in a multi-tenant database environment, comprising:

sending, by an administrative device, a request to log in to a server associated with a first domain;

receiving, by an administrative device, a session identification allowing the user to log into the server associated with the first domain;

sending, by the administrative device, a substitute user request to the server associated with a first domain, the substitute user request including a request for the user of the administrative device to become a user on a second domain;

receiving, by the administrative device, prepared data allowing the user of the administrative device to login to an application on the second domain; and

sending, by the administrative device, the prepared data to a second server associated with the second domain to thereby allow the user of the administrative device to login to the application on the second domain.

2. The method of claim 1, wherein prepared data includes an encrypted session identification, an encrypted internet protocol address of the user of the administrative device and an encrypted target user identification, the target user identification corresponding to a user of the second domain.

3. The method of claim 1, further comprising receiving, by the administrative device, a session identification allowing the user of the administrative device to login to the application on the second domain.

4. The method of claim 3, further comprising:

sending, by the administrative device, a request to log out of the application on the second domain; and

receiving, by the administrative device, a new session identification allowing the user to return to the first domain.

5. A system for logging into an application across separate domains in a multi-tenant database environment, comprising:

a first server associated with a first domain; and

a second server associated with a second domain, the second server hosting an application for a tenant of the multi-tenant database environment on the second domain,

wherein the first server is configured to;

receive a substitute user request from a user of the first domain, the substitute user request including a request for the user of the first domain to become a user on a second domain;

prepare data allowing the user of the first domain to login to the application on the second domain;

send the prepared data to the user of the first domain; and

redirect the user of the first domain to a second server associated with the second domain to thereby allow the first user of the first domain to post the data.

6. The system of claim 5, wherein the second server is configured to:

receive the prepared data from the user of the first domain;

validate the received prepared data; and

send, if the prepared date is validated, a new session identification to the user of the first domain allowing the user of the first domain to login to the application on the second domain.

7. The system of claim 5, wherein the a first server and the second server each include a servlet to manage the substitute user request.

8. The system of claim 5, wherein the prepared data includes an encrypted session identification of the user of the first domain, an internet protocol address of the user of the first domain and a target user identification.

9. The system of claim 8, wherein the validating further comprises decrypting the encrypted internet address protocol and compare the decrypted internet address protocol with the internet address protocol from where the prepared data originated;

and

verifying that the prepared data is valid if the decrypted internet address protocol matches the internet address protocol from where the substitute user request originated.

10. The system of claim 6, wherein session identification is sent using a HTTP put instruction.

11. The system of claim 6, wherein the new session identification limits the user of the first domain from modifying application data on the second domain.

12. The system of claim 10, wherein second server is further configured to:

receive a request to log out of the application from a user of the first domain; and

send, after receiving the request to log out of the application, a previous session identification to the user of the first domain redirecting the user of the first domain back to the first domain.

16. The method of claim 12, wherein the preparing further comprises encrypting, by the server associated with the first domain, an internet protocol address where the request to log onto the second domain originated.

17. The method of claim 16, wherein the validating, by a server associated with the second domain, of the prepared data further comprises decrypting, by the server associated with the second domain, the encrypted internet address protocol and comparing the decrypted internet address protocol with an internet address protocol from where the server associated with the second domain receive the prepared data.

13. A method for logging into a second domain from a first domain, comprising:

receiving, by a server associated with the first domain, a request to log onto the second domain;

preparing, by the server associated with the first domain, data allowing the user of the first device to login to the second domain; and

sending, by the server associated with the first domain, the prepared data to the user of the first domain and redirecting the user of the first domain to a second server associated with the second domain to thereby allow the first user of the first domain to post the prepared data.

14. The method of claim 13, further comprising:

receiving, by a server associated with the second domain, the prepared data from the user of the first domain;

validating, by a server associated with the second domain, the received prepared data; and

sending, by a server associated with the second domain, a new session identification, if the prepared date is validated, to the user of the first domain allowing the user of the first domain to login to the application on the second domain.

15. The method of claim 14, wherein the new session identification is sent using a HTTP put instruction.

18. The method of claim 14, further comprising:

receiving, by the server associated with the second domain, a request to log out of the second domain; and

sending, by the server associated with the second domain, another session identification allowing the user of the first domain to return to the first domain.

19. The method of claim 13, wherein the first domain is an administrative domain.

20. The method of claim 14, wherein the new session identification limits the user of the first domain from modifying data on the second domain.