Indexing secure enterprise documents using generic references

• US 8,626,794 B2
• Filed: 07/02/2012
• Issued: 01/07/2014
• Est. Priority Date: 03/01/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Liao, Ciya, Chang, Thomas, Krishnaprasad, Muralidhar, Bhavsar, Meeten
• Primary Examiner(s): Woo, Isaac M
• Application Number:
  US13/539,622
• Publication Number:
  US 20130173582A1
• Time in Patent Office: 554 Days
• Field of Search: 707600-899
• US Class Current: 707/791
• CPC Class Codes: G06F 16/2228 Indexing structures
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: G06F 16/93 Document management systems
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/9538 Presentation of query results
• CPC Class Codes: G06F 21/31 User authentication
• CPC Class Codes: G06F 21/6227 where protection concerns the structure of data, e.g. records, types, queries
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• 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/102 Entity profiles

Abstract

A web crawler indexes documents including information about document contents and metadata including information such as a URL. However, some applications rely on URL'"'"'s that change frequently or are constructed to include user information so that the contents retrieved is customized to the user. An approach is provided for storing generic URL'"'"'s in an index at crawl time, which are customized for the user at search time. A callback mechanism may be used to dynamically transform the generic URL into a URL that is specific to the user issuing the query and/or includes current information that may change frequently. In this way, when the query or search results are returned to the user, the user receives links that are active and valid for that particular user, directing the user to the appropriate site, application, etc. without requiring continuous updating of a very large index.

Claims

1. A method of providing access to secure documents in an enterprise system comprising:

crawling a secure data source;

generating, by a processor, indexing information about a plurality of secure documents stored in the enterprise system;

wherein the indexing information for each secure document of the plurality of secure documents includes a generic URL to said each secure document;

receiving a query for searching the secure data source;

in response to the query, using, by a processor, the indexing information to identify a set of documents, wherein each document of the set of documents satisfies the query and is associated with one or more security attributes;

for each document of the set of documents;

accessing, by a processor, an identity management system to obtain a security attribute value for each of the one or more security attributes associated with said each document; and

responding to the query by providing a link to said each document, wherein the link is generated based at least on the generic URL to said each document and the security attribute value obtained from the identity management system for each of the one or more security attributes associated with said each document.

2. The method of claim 1, wherein accessing the identity management system further comprises calling back into the identity management system.

3. The method of claim 2, wherein calling back into the identity management system comprises obtaining information including one or more of:

role information, group information, or project information.

4. The method of claim 1, the method further comprising:

providing a framework to include a plurality of application program interfaces (APIs), each API operable to communicate with a respective secure data source and associated identity management system.

5. The method of claim 1, wherein the one or more security attribute values are for a user;

and

the method further comprising;

determining that the user cannot be validated; and

in response to determining that the user cannot be validated, denying the user access to the secure data source.

6. The method of claim 1, the method further comprising:

providing an additional API to allow user identification information to be passed to an additional secure data source.

7. The method of claim 6, the method further comprising consolidating results of the query from the secure data source and the additional secure data source.

8. A non-transitory computer-readable storage medium for storing sets of instructions that provide access to secure documents in an enterprise system, the sets of instructions, which when executed by a computer, cause the computer to:

crawl a secure data source;

generate indexing information about a plurality of secure documents stored in the enterprise system;

wherein the indexing information for each secure document of the plurality of secure documents includes a generic URL to said each secure document;

receive a query to the secure data source;

in response to the query, use the indexing information to identify a set of documents, wherein each document of the set of documents satisfies the query and is associated with one or more security attributes;

for each document of the set of documents;

access an identity management system to obtain a security attribute value for each of the one or more security attributes associated with said each document; and

respond to the query by providing a link to said each document, wherein the link is generated based at least on the generic URL to said each document and the security attribute value obtained from the identity management system for each of the one or more security attributes associated with said each document.

9. The non-transitory computer-readable storage medium of claim 8, wherein the set of instructions that cause the computer to access the identity management system further comprises instructions that cause the computer to call back into the identity management system.

10. The non-transitory computer-readable storage medium of claim 8, further comprising instructions which when executed by the computer, further cause the computer to obtain access to information including one or more of:

role information, group information, or project information.

11. The non-transitory computer-readable storage medium of claim 8,

wherein the one or more security attribute values are for a user;

and

further comprising instructions, which when executed by the computer, cause the computer to;

determine that the user cannot be validated; and

in response to determining that the user cannot be validated, deny the user access to the secure data source.

12. The non-transitory computer-readable storage medium of claim 11, further comprising instructions, which when executed by the computer, cause the computer to provide an additional API to allow user identification information to be passed to an additional secure data source.

13. The non-transitory computer-readable storage medium of claim 11, further comprising instructions, which when executed by the computer, cause the computer to obtain project information associated with the user.

14. A system comprising:

a processor;

a memory coupled to the processor;

the memory storing instructions for;

crawling a secure data source;

generating indexing information about a plurality of secure documents stored in the enterprise system;

wherein the indexing information for each secure document of the plurality of secure documents includes a generic URL to said each secure document;

receiving a query to the secure data source;

in response to the query, using the indexing information to identify a set of documents, wherein each document of the set of documents satisfies the query and is associated with one or more security attributes;

for each document of the set of documents;

accessing an identity management system to obtain a security attribute value for each of the one or more security attributes associated with said each document; and

responding to the query by providing a link to said each document, wherein the link is generated based at least on the generic URL to said each document and the security attribute value obtained from the identity management system for each of the one or more security attributes associated with said each document.

15. The system of claim 14, wherein the instructions for accessing the identity management system further comprise instructions for calling back into the identity management system.

16. The system of claim 15, wherein the instructions for calling back into the identity management system further comprise instructions for obtaining information including one or more of:

role information, group information, or project information.

17. The system of claim 14, wherein the instructions further comprise instructions for providing a framework to include a plurality of application program interfaces (APIs), each API operable to communicate with a respective secure data source and associated identity management system.

18. The system of claim 14, wherein the one or more security attribute values are for a user;

and

the instructions further comprising instructions for;

determining that the user cannot be validated; and

in response to determining that the user cannot be validated, denying the user access to the secure data source.

19. The system of claim 14, wherein the instructions further comprise instructions for providing an additional API to allow user identification information to be passed to an additional secure data source.

20. The system of claim 19, wherein the instructions further comprise instructions for consolidating results of the query from the secure data source and the additional secure data source.