[
https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16333455#comment-16333455 ]
Jacques Le Roux commented on OFBIZ-9557:
----------------------------------------
A checkbox would be OK, but, for security reason, not OOTB. Because once you have access to this screen you could do what you want with jobs. OFBiz users must take the responsability for that. So I'd recommend introducting a security (seems most fitting) property, like
bq. runJobAsSystemUser=false
This would be used for showing the checkbox and bypassing the LDAP authentication in code
> Add the ability to schedule a job to run as a system/service user
> -----------------------------------------------------------------
>
> Key: OFBIZ-9557
> URL:
https://issues.apache.org/jira/browse/OFBIZ-9557> Project: OFBiz
> Issue Type: Improvement
> Components: tools
> Reporter: Matthew Mulligan
> Priority: Major
>
> When scheduling a job it automatically schedules it to run as the user that created the schedule. The issue comes up when that users password changes.
> We use LDAP authentication and our passwords change every 90 days. Right now every 90 days when my password changes I have to delete all previously scheduled jobs and recreate them.
> What would be nice is an option when scheduling the job to Run as System account or Run as User and be able to put the users name in.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
Locked
