Knowledgebase Home Page  >  SearchUnit  >  Version 3 Articles
Search the Knowledge Base
What CAS (code access security) permissions are required to use Search for ASP.NET? (Version 3)
https://keyoti.com/kb/Default.aspx?ToDo=view&questId=132&catId=67

Options

Print this page
Email this to a friend

 

The trust level required to use Search for ASP.NET is dependent on the operation.  If the control DLLs have been installed in the GAC (e.g. if you used the installer) then under usual server configuration they will be given Full trust and the following does not apply.  If however the control DLLs are not in the GAC, then the actual trust level given to them is dependent on the server configuration (typically for example, hosting companies use Medium trust).  We present here details of what ASP.NET trust level is required for any operation, and any special considerations when operating under partial (less than Full) trust.

 

For an overview of trust levels and CAS under ASP.NET, please see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnnetsec/html/thcmch09.asp

 

[Please note that some features below are not present in Search Lite, or in versions prior to 2.2]

 

 

Search (using the SearchResult control, or the SearchAgent class)

 

Levels: Works with Low, Medium, High and Full trust levels.

 

Considerations: When working with trust levels at or below Medium, the Index Directory must be under the application root.  If it isn't, an exception is thrown.

 

 

 

Crawl (when run from an ASP.NET application, such as the Admin application)

 

Levels: Works with Medium, High and Full trust levels.

 

Considerations: When working with Medium trust levels the Index Directory must be under the application root, and the originUrl must be specified in the config as the site being crawled (http://msdn2.microsoft.com/en-us/library/tkscy493.aspx), eg originUrl="http://localhost/.*"

 

 

 

Build (when run from an ASP.NET application, such as the Admin application)

 

Levels: Works with Medium, High and Full trust levels.

 

Considerations: When working with Medium trust levels the Index Directory must be under the application root, and the originUrl must be specified in the config as the site being crawled (http://msdn2.microsoft.com/en-us/library/tkscy493.aspx), eg originUrl="http://localhost/.*"

 

 

 

 

File System Scan

 

Levels: Works with Medium, High and Full trust levels.

 

Considerations: When working with Medium trust levels the Index Directory must be under the application root, and the directory being scanned must also be under the application root.

 

 

 

 

DataSet Import (when run from an ASP.NET application, such as the Admin application)

 

Levels (with OLE DB connections): Works with Full trust level only.

Levels (with MSSQL connections): Works with Medium, High and Full trust

 

Considerations: 'Integrated Security' is allowed only under Full trust.

 

 

 

SearchSuggestions Control (spelling check control)

 

Levels: Works with Low, Medium, High and Full trust levels.

 

Considerations: None.

 

 

 

SearchOptions Control

 

Levels: Works with Full trust only (see considerations).

 

Considerations: This control is not compatible with partial trust environments because it uses various design time features to generate object instances.  Therefore it is recommended that for partial trust environments that a custom search options user control is created, as per the example in the Search Pro demo project.  This allows regular UI controls to be used to give the user options.

 

 

 

 

FeaturedResults Control

 

Levels: Works with Low, Medium, High and Full trust (see considerations).

 

Considerations: This control uses various design time features to generate object instances, which are not partial trust compatible.  For a simple workaround please see /kb/Default.aspx?ToDo=view&questId=130&catId=54

 

 

 

If you have further questions please email support@keyoti.com

 


Related Questions:

Attachments:

No attachments were found.