[jira] [Commented] (OFBIZ-10573) can‘t run job when user changed password

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (OFBIZ-10573) can‘t run job when user changed password

Nicolas Malin (Jira)

    [ https://issues.apache.org/jira/browse/OFBIZ-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16666098#comment-16666098 ]

Rohit Koushal commented on OFBIZ-10573:
---------------------------------------

In the OFBIZ-9557, I have added a support to run Job as system user. Now here I think we need to handle the case when user manually update the password and jobs gets fail due to the password change.

So here I think we can handle the case like if password gets updated and mismatch occur then we can check it in the UserLoginPasswordHistory for the immediate old password in ServiceDispatcher and if found then we can use the new the updated user login(which having new password) to run job and save this userLogin in the RunTime data for further job execution(if it is recurring).

Please review and let me know if you think this solution is acceptable.

> can‘t run job when user changed password
> ----------------------------------------
>
>                 Key: OFBIZ-10573
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-10573
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: Release Branch 13.07, Release Branch 16.11
>            Reporter: zhang.liang
>            Assignee: Pierre Smits
>            Priority: Blocker
>         Attachments: image-2018-09-19-15-41-13-122.png, image-2018-09-19-15-43-25-388.png
>
>
> dispatcher.runAsync()   create a job. if user changed password befor run job, throw a exception
> !image-2018-09-19-15-41-13-122.png!
> ServiceDispatcher.chekAuth();
> !image-2018-09-19-15-43-25-388.png!
> if check old password not equals new password  auth failed
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)