Search hit URL modification for secure application integration

• US 9,251,364 B2
• Filed: 12/30/2013
• Issued: 02/02/2016
• Est. Priority Date: 03/01/2006
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Ture, Mark, Krishnaprasad, Muralidhar, Delgado, Joaquin
• Primary Examiner(s): HOLDER, BRADLEY W
• Application Number:
  US14/144,315
• Publication Number:
  US 20140114946A1
• Time in Patent Office: 764 Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques
• CPC Class Codes: G06F 21/53 by executing in a restricted environment, e.g. sandbox or secure virtual machine
• 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 63/20 for managing network security; network security policies in general filtering policies H04L63/0227

Abstract

A flexible and extensible architecture allows for secure searching across an enterprise. Such an architecture can provide a simple Internet-like search experience to users searching secure content inside (and outside) the enterprise. The architecture allows for the crawling and searching of a variety of sources across an enterprise, regardless of whether any of these sources conform to a conventional user role model. The architecture further allows for security attributes to be submitted at query time, for example, in order to provide real-time secure access to enterprise resources. The user query also can be transformed to provide for dynamic querying that provides for a more current result list than can be obtained for static queries.

Claims

1. A method for dynamically accessing secure content, comprising:

crawling a group of documents in a secure data source;

indexing, using a processor, each crawled document;

storing, in an index, document metadata for said each crawled document and a generic link for said each crawled document;

receiving a query from an authenticated user, wherein the query is received as part of a user session;

locating, using the index, an indexed document in the group of documents in the secure data source that satisfies the query from the authenticated user;

sending a callback to the secure data source from which the indexed document was crawled, the callback including the metadata for the indexed document, the link for the indexed document, and user session information;

receiving, from the secure data source and in response to the callback, updated metadata information for the indexed document, wherein the updated metadata information for the indexed document is different from the document metadata stored in the index for the indexed document;

building current document metadata for the indexed document using the updated metadata information;

receiving, in response to the callback, updated link information that is based on the existing generic link and the user session information, wherein the updated link information encodes at least part of the user session information and is a valid link for the authenticated user at the time of the query;

building a current link for the indexed document using the updated link information; and

providing the current link for the indexed document and the current document metadata for the indexed document to be displayed as a search result responsive to the query.

2. The method according to claim 1, further comprising crawling documents both inside and outside of an enterprise.

3. The method according to claim 1, wherein the current link is an active and valid link for only the authenticated user.

4. The method according to claim 1, wherein the generic link is not an active and valid link.

5. The method according to claim 1, wherein the generic link is not a valid link, and the current link is updated from the existing generic link using user security attribute values of the authenticated user.

6. The method according to claim 1, wherein the current link points to an attachment of an email message and the generic link points to a main body of the email message.

7. The method according to claim 6, wherein the current link is updated from the generic link at query time.

8. The method according to claim 1, wherein building current document metadata includes modifying a document title or summary of the indexed document into an appropriate language for the user.

9. A computer system comprising:

one or more hardware processors; and

one or more memory devices comprising instructions that, when executed by the one or more hardware processors, configure the one or more hardware processors to;

crawl a group of documents in a secure data source;

index each crawled document;

store, in an index, document metadata for said each crawled document and a generic link for said each crawled document;

receive a query from an authenticated user, wherein the query is received as part of a user session;

locate, using the index, an indexed document in the group of documents in the secure data source that satisfies the query from the authenticated user;

send a callback to the secure data source from which the indexed document was crawled, the callback including the metadata for the indexed document, the link for the indexed document, and user session information;

receive, from the secure data source and in response to the callback, updated metadata information for the indexed document, wherein the updated metadata information for the indexed document is different from the document metadata stored in the index for the indexed document;

build current document metadata for the indexed document using the updated metadata information;

receive, in response to the callback, updated link information that is based on the existing generic link and the user session information, wherein the updated link information encodes at least part of the user session information and is a valid link for the authenticated user at the time of the query;

build a current link for the indexed document using the updated link information; and

provide the current link for the indexed document and the current document metadata for the indexed document to be displayed as a search result responsive to the query.

10. The system according to claim 9, wherein the callback is sent through an application programming interface to the secure data source.

11. The system according to claim 9, wherein the current link is an active and valid link for only the authenticated user.

12. The system according to claim 9, wherein the generic link is not an active and valid link.

13. The system according to claim 9, wherein the current link points to an attachment of an email message and the generic link points to a main body of the email message.

14. The system according to claim 9, wherein the current link is updated from the generic link at query time.

15. A non-transitory computer-readable storage medium comprising instructions that, when executed by one or more hardware processors, cause the one or more hardware processors to perform operations comprising:

crawling a group of documents in a secure data source;

indexing each crawled document;

storing, in an index, document metadata for said each crawled document and a generic link for said each crawled document;

receiving a query from an authenticated user, wherein the query is received as part of a user session;

locating, using the index, an indexed document in the group of documents in the secure data source that satisfies the query from the authenticated user;

sending a callback to the secure data source from which the indexed document was crawled, the callback including the metadata for the indexed document, the link for the indexed document, and user session information;

receiving, from the secure data source and in response to the callback, updated metadata information for the indexed document, wherein the updated metadata information for the indexed document is different from the document metadata stored in the index for the indexed document;

building current document metadata for the indexed document using the updated metadata information;

receiving, in response to the callback, updated link information that is based on the existing generic link and the user session information, wherein the updated link information encodes at least part of the user session information and is a valid link for the authenticated user at the time of the query;

building a current link for the indexed document using the updated link information; and

providing the current link for the indexed document and the current document metadata for the indexed document to be displayed as a search result responsive to the query.

16. The non-transitory computer-readable storage medium according to claim 15, wherein building the current document metadata for the indexed document using the updated metadata information comprises modifying a document title or summary of the indexed document into an appropriate language for the authenticated user.

17. The non-transitory computer-readable storage medium according to claim 15, comprising additional instructions that, when executed by the one or more hardware processors, cause the one or more hardware processors to perform operations comprising crawling documents both inside and outside of an enterprise.

18. The non-transitory computer-readable storage medium according to claim 15, wherein the current link is an active and valid link for only the authenticated user.

19. The non-transitory computer-readable storage medium according to claim 15, wherein the generic link is not an active and valid link.

20. The non-transitory computer-readable storage medium according to claim 15, wherein the generic link is not a valid link, and the current link is updated from the existing generic link using user security attribute values of the authenticated user.