topic Re: Search & Authentication in Alfresco Archive

Search & Authentication

rogier_oudshoor — Fri, 14 Dec 2007 10:33:44 GMT

I am developing a community site based on alfresco webscripts. We have an issue with using search.From what i've seen, when i use the search API from javascript, the search will return all items that the logged in user has access to.However, when i use Java-based search (which i have to, because i w

Re: Search & Authentication

mikeh — Fri, 14 Dec 2007 10:44:51 GMT

(which i have to, because i want to order the results)

What problems are you having sorting the results in Javascript?

Mike

Re: Search & Authentication

rogier_oudshoor — Fri, 14 Dec 2007 10:48:16 GMT

Well, when i look at the documentation (at http://wiki.alfresco.com/wiki/JavaScript_API#Search_API ), there is no way to sort the results except programmatically. Typically, a search may return hundreds of results … of which i'd only like to process the first 50 or so. Ordering by code would mean a huge overhead, which i'd like to avoid by having Lucene order the results.

If i can order & limit the results via JavaScript, i'd be quite happy

Re: Search & Authentication

rogier_oudshoor — Wed, 19 Dec 2007 11:00:33 GMT

After a long search, i found what was causing this.

I was using spring beans to set the searchService to my own search implementation. The given searchService has admin access.

Alfresco's search implementation retrieves the searchService at runtime via the serviceRegistry. This searchService has the access of the current user.

This method appears to apply to all of Alfresco's services. Basically, if you want to do something that requires admin access, you can get the services directly from Spring. If you want to be restricted by the users' capabilities, you need to retrieve the services dynamically via the serviceRegistry.

Personally, i feel this is poor design - i'd be much happier if you could tell the service what kind of access you'd like to use. Any thoughts?

Re: Search & Authentication

rraulji — Wed, 20 Aug 2008 16:41:38 GMT

Hi Rogier,

Did u find a way to sort and even restrict the number of results returned by Alfresco's Javascript API for search ?

Re: Search & Authentication

rogier_oudshoor — Thu, 21 Aug 2008 06:20:21 GMT

Hi rraulji,

The only way to sort (as far as i know) is using the Java API. That means that, if you want to use call from Javascript, that you will have to code your own BaseScopableProcessorExtension to implement it.

Cheers,

Rogier

Re: Search & Authentication

mikeh — Thu, 21 Aug 2008 07:44:19 GMT

From v2.9 the JavaScript search API supports sorting (added in SVN r1214 30-Oct-2007)

search.luceneSearch(query, sortColumn, sortAscending);‍

e.g. search.luceneSearch(query, "@cm:created", true);

Thanks,
Mike

Re: Search & Authentication

satishvarmadand — Tue, 16 Dec 2008 01:16:18 GMT

Hi,
How can i incorporate detailed search in web-services API . I would like to incorporate
1) Sorting
2) Pagination like get search results from 1 -> 100 etc.. or give me only first 100 results etc.

Currently I am using something like this

Query query = new Query(Constants.QUERY_LANG_LUCENE, searchQuery);
QueryResult queryResult = WebServiceFactory.getRepositoryService().query(storeRef, query, false);

So how can i add "addSort" flag.

I found out that SearchParameters enables this. but webserice Repository service does not support this (only foundation repository service)

Also , while constructing the PATH query, how can i specify list of values
For Ex: PATH:"/app:company_home/cmBM//*" AND TEXT:"document"

so Instead of passing 1 value (document) for TEXT filed, how i can i pass array to values (instead of converting to OR and ANDs) for a specific meta-data field (which is multi-value attribute).

Any help would be greatly appreciated.

Thanks

Re: Search & Authentication

t_broyer — Wed, 17 Dec 2008 11:12:41 GMT

After a long search, i found what was causing this.

I was using spring beans to set the searchService to my own search implementation. The given searchService has admin access.

Alfresco's search implementation retrieves the searchService at runtime via the serviceRegistry. This searchService has the access of the current user.

This method appears to apply to all of Alfresco's services. Basically, if you want to do something that requires admin access, you can get the services directly from Spring. If you want to be restricted by the users' capabilities, you need to retrieve the services dynamically via the serviceRegistry.

Personally, i feel this is poor design - i'd be much happier if you could tell the service what kind of access you'd like to use. Any thoughts?

Just use the "SearchService" rather than the "searchService". The "SearchService" is the one you'd get from the service registry, without the need for the service registry…

Re: Search & Authentication

rogier_oudshoor — Mon, 16 Feb 2009 08:19:47 GMT

Just use the "SearchService" rather than the "searchService". The "SearchService" is the one you'd get from the service registry, without the need for the service registry…

Do you know if this holds true for all services? I.E., if there is a NodeService with ACL checking and a nodeService without it?

Re: Search & Authentication

t_broyer — Mon, 16 Feb 2009 08:43:24 GMT

Almost, yes.

Have a look at the public-*-context.xml files in WEB-INF/classes/alfresco.