System user and the search API, not finding some sites
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2013 10:59 AM
I am really not sure whether this is the right place to post or where to post this question. Please let me know if it needs to be posted elsewhere.
I have been using the search API for a query as TYPE:"st:site" that is running through a schedule JS webscript using the Execute
ScriptJob, which I believe is running as the system user. The problem I have is that it is not finding all the sites I am expecting it to, and I am struggling to identify why it is missing some and not others. The same query running through the search on the node browser returns the sites I was expecting, which I assume is because it is running as admin.
I have seen similar behaviour in the past but have got round it by running as admin user, as it was in a Java webscript.
My question is shouldn't the system user have access to everything? And if so what might be going wrong in this case?
Thanks in advance
Garry
I have been using the search API for a query as TYPE:"st:site" that is running through a schedule JS webscript using the Execute
ScriptJob, which I believe is running as the system user. The problem I have is that it is not finding all the sites I am expecting it to, and I am struggling to identify why it is missing some and not others. The same query running through the search on the node browser returns the sites I was expecting, which I assume is because it is running as admin.
I have seen similar behaviour in the past but have got round it by running as admin user, as it was in a Java webscript.
My question is shouldn't the system user have access to everything? And if so what might be going wrong in this case?
Thanks in advance
Garry
Labels:
- Labels:
-
Archive
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-21-2013 11:01 AM
Just to add to the above, I am currently using 4.0.d and have not verified whether the same occurs on 4.2.
