[Exist-development] Scheduler and new permissions model....

[Andrzej J. T. <an...@ch...>]

Adam:

I've got a test environment running your latest permissions code (current SVN). I was hoping that
Wolfgang's recent checkin might have fixed the duplicated attributes bug, but unfortunately it
didn't.  So I plan to dive into the cause of that later this week, since I haven't been able to
create a replicable, simple test case as I usually do.

In the meantime, in our environment we fire off some scheduled User XQuery tasks from the conf.xml
file at startup.

Problem was, that our user jobs are now failing with the following exception:

2011-06-14 16:05:04,496 [DefaultQuartzScheduler_Worker-2] INFO  (JobRunShell.java [run]:221) - Job
eXist.User.XQuery: /db/chaeron/raven/common/xquery/chaeronJobScheduler.xql threw a
JobExecutionException:
org.quartz.JobExecutionException: UserXQueryJob Failed: Permission denied for the scheduling user:
guest! Unscheduling UserXQueryJob.
	at org.exist.scheduler.UserXQueryJob.abort(UserXQueryJob.java:268)
	at org.exist.scheduler.UserXQueryJob.abort(UserXQueryJob.java:263)
	at org.exist.scheduler.UserXQueryJob.execute(UserXQueryJob.java:228)
	at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
	at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:549)

found in the scheduler.log file.

It seems that the scheduler cannot even initiate the user xquery any more due to the permissions
stuff, whereas in the past this was fine. In fact, in the documentation found in conf.xml, it
specifically states that the a user xquery will be started running as guest, but then can change the
login using xquery functions to perform controlled things, which is in fact what our xquery does.
But it doesn't even get to that stage, since the permissions stuff is not allowing the scheduled
xquery to even fire.

I'm not sure of how we fix this?  Do we need to set global execute permissions on all the xqueries
we have stored in the database, or at least on the ones that are scheduled at startup from conf.xml?
 Do we need to extend the conf.xml scheduler elements/definitions to be able to specify what user
should be used to fire up a scheduled xquery, rather than the default guest?

Your advice on the best way to proceed would be much appreciated.

Thanks!

-- 
Andrzej Taramina
Chaeron Corporation: Enterprise System Solutions
http://www.chaeron.com