SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FOR ENABLING ACCESS TO A RESOURCE OF A MULTI-TENANT ON-DEMAND DATABASE SERVICE UTILIZING A TOKEN

• US 20130198236A1
• Filed: 03/11/2013
• Published: 08/01/2013
• Est. Priority Date: 09/12/2008
• Status: Active Grant

• Current Assignee: Salesforce.com, Inc.
• Original Assignee: Salesforce.com, Inc.
• Inventors: Lissack, Ryan, Fly, Robert Charles, Snell, Robert Joseph
• Granted Patent: US 8,825,704 B2
• Time in Patent Office: Days
• US Class Current: 707/783
• CPC Class Codes: G06F 16/11 File system administration, e.g. details of archiving or snapshots file system backup G06F11/14
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06
• CPC Class Codes: G06F 16/176 Support for shared access to files; File sharing support
• CPC Class Codes: G06F 16/22 Indexing; Data structures therefor; Storage structures
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 21/335 for accessing specific resources, e.g. using Kerberos tickets
• CPC Class Codes: G06F 21/62 Protecting access to data via a platform, e.g. using keys or access control rules
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: G06F 2221/2117 User registration
• CPC Class Codes: G06F 2221/2119 Authenticating web pages, e.g. with suspicious links
• CPC Class Codes: G06F 2221/2141 Access rights, e.g. capability lists, access control lists, access tables, access matrices
• CPC Class Codes: H04L 45/20 Hop count for routing purposes, e.g. TTL
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0838 using one-time-passwords
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

In accordance with embodiments, there are provided mechanisms and methods for enabling access to a resource of a multi-tenant on-demand database service utilizing a token. These mechanisms and methods for enabling access to a resource of a multi-tenant on-demand database service utilizing a token can be utilized to prevent identification of a user attempting to access the resource, and thus unwanted use of the user'"'"'s identity.

Claims

1. A method, comprising:

receiving, at a first domain, a request from a user to make records accessible;

generating a token unique to the request;

tagging the records specified by the request with the token and executable computer code to provide access to the records;

sending the token to the user;

receiving, at a second domain, a request to access the records, the request including the token;

determining whether the records of the request to access the records includes the token; and

permitting access to at least one record containing the token by executing the computer code.

2. The method of claim 1, wherein the request to access the records includes a request to download the records.

3. The method of claim 1, wherein the token is automatically generated on-demand in response to the receipt of the request to make the records accessible.

5. The method of claim 1, wherein each of the records is further tagged with an identifier of the user.

6. The method of claim 1, wherein the first domain of the multi-tenant on-demand database service includes a first server of a multi-tenant on-demand database service and the second domain of the multi-tenant on-demand database service includes a second server of the multi-tenant on-demand database service.

7. The method of claim 1, wherein the request to access the records is received from a device of the user.

8. The method of claim 1, wherein the token is verified utilizing the second domain,

9. The method of claim 8, wherein access to the records by the user is prevented in response to a failure of the verification of the token.

4. The method of claim I, wherein the token includes a randomly generated identifier.

10. The method of claim 18, wherein the token includes a time-to-live and is verified by determining that the token is stored and that the token has not expired.

11. A computer program product e bodied on a non-transitory computer readable medium, comprising:

computer code for receiving, at a first domain, a request from a user to make records accessible;

computer code for generating a token unique to the request;

computer code for tagging the records specified by the request with the token and executable computer code to provide access to the records;

computer code for sending the token to the user;

computer code for receiving, at a second domain, a request to access the records, the request including the token;

computer code for determining whether the records of the request to access the records includes the token; and

computer code for permitting access to at least one record containing the token by executing the computer code.

12. An apparatus, comprising:

a first domain including at least one first processor for;

receiving a request from a user to make records accessible,

generating a token unique to the request, and

tagging the records specified by the request with the token and executable computer code to provide access to the records,

sending the token to the user; and

a second domain including at least one second processor for;

receiving a request to access the records, the request including the token,

determining whether the records of the request to access the records includes the token, and

permitting access to at least one record containing the token by executing the computer code.