[
https://issues.apache.org/jira/browse/OFBIZ-9557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16223269#comment-16223269 ]
Rohit Koushal commented on OFBIZ-9557:
--------------------------------------
I can see two solutions to this problem :
1. We can introduce a property setting which bypass LDAP authentication and use the inbuilt system authentication engine(OFBiz ) when jobs run from job server.
2. We can add a checkbox to run a job as system on [Schedule Job|
https://localhost:8443/webtools/control/scheduleJob] screen and bypass the LDAP authentication in case of system user.
If anyone have even better options then feel free to discuss it here.
> 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
>
> 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
(v6.4.14#64029)
Locked
