[
https://issues.apache.org/jira/browse/ISIS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Haywood resolved ISIS-664.
------------------------------
Resolution: Won't Fix
Instead, the original user is available through the CommandContext class. So
any code that specifically wishes to discriminate between the real user running
the command and the effective user that originally initiated the command should
use CommandContext.getCommand().getUser(), rather than through the
DomainObjectContainer.
> Provide an abstract class for running "sudo" scheduler jobs
> -----------------------------------------------------------
>
> Key: ISIS-664
> URL: https://issues.apache.org/jira/browse/ISIS-664
> Project: Isis
> Issue Type: New Feature
> Components: Core, Objectstore: JDO
> Affects Versions: objectstore-jdo-1.3.0, core-1.3.0
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Priority: Minor
> Fix For: objectstore-jdo-1.4.0, core-1.4.0
>
>
> To be used as the basis for Quartz scheduler jobs, say... but do not bring in
> a dependency on Quartz.
> The main work here is in extending the security APIs to enable "sudo". This
> will enable persisted BackgroundTaskJdo entities (from ISIS-661) to be run as
> the user that created them.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
