1 of 1 people found this helpful
Hi Jimmy ,
From other forum posts and my experiments what I found is that the better way for identity managment is to use the UserGroupCallback interface. Using this you can avoid implicit addition of users/groups in runtime.
org.jbpm.task.service.UserGroupCallback is the interface provided for this purpose.
The interface has three methods :
- boolean existsUser(String userId)
Validates whether the input userid is valid for your application. If you are doing an evaluation , always return a true, the user assigned to the task in the process definition would be automatically added to the
ORGANIZATIONALENTITY table ( magic )
- boolean existsGroup(String groupId)
Validates whether the input groupId is valid for your application.Similar to above for evaluation we can return true and the above magic repeats.
- List<String> getGroupsForUser(String userId, List<String> groupIds, List<String> allExistingGroupIds)
Never tried this, but as in case of the other methods , the method signature says it all..
Check section 13.2.4
Just shared my thoughts may be it would help you .
Cool !!!But this api is provided in jbpm5.3,can I use version 5.3 now?
I have tried this in 5.2 and is working
I will upgrade my jbpm version!