topic Re: Identity Service for Process Engine Only - No Explorer in Alfresco Archive

Identity Service for Process Engine Only - No Explorer

taruntyagi — Sun, 03 Aug 2014 17:41:30 GMT

HiWe intend to use Activiti within a J2EE Spring application. There will be user tasks and groups. I have tried implementing custom user and group entity managers , but they never seem to be called when a user task is assigned or when I query tasks for a user or group.I suppose , the process engine

Re: Identity Service for Process Engine Only - No Explorer

frederikherema1 — Wed, 06 Aug 2014 08:26:52 GMT

Your assumption is partially correct

1. Adding assignee, candidate groups, candidate starters, … to the process definitions and task will not trigger any identity-related calls. The engine is implemented (explicit choice to keep the implementation as flexible as possible) in such a way that there is NO explicit checking of identities against the user-management. So *any* value for assignee will work, even if it's not a valid user. If you want to have this enforces, the layer above the engine API (your code) should check this.

2. When requesting tasks assigned to a specific user, the Identity management is indeed not used. Only when calling TaskService.taskCandidateUser(…), all groups for that user will be requested from the identity-management and included in the query - the resulting tasks include tasks where user X is a candidate explicitly and also all tasks where you're member of at least one candidate group…

Does this clarify it for you?

Re: Identity Service for Process Engine Only - No Explorer

arnoldschrijve1 — Wed, 06 Aug 2014 08:55:13 GMT

I may add another thing I just found out which may be helpful. And that is that some of the examples of using custom session factories, that can be found by googling, return the UserEntityManager.class and GroupEntityManager.class abstract classes in getSessionType() instead of the interface UserIdentityManager, GroupIdentityManager. So if you started from that code it won't work.

After changing this my custom group + user managers are called:

<java>

package com.example.workflow.identity;

import org.activiti.engine.impl.interceptor.Session;
import org.activiti.engine.impl.interceptor.SessionFactory;
import org.activiti.engine.impl.persistence.entity.UserIdentityManager;

public class CustomUserManagerFactory implements SessionFactory {

@Override
public Class<?> getSessionType() {
return UserIdentityManager.class;
}

@Override
public Session openSession() {
return new CustomUserManager();
}

}

</java>

Re: Identity Service for Process Engine Only - No Explorer

arnoldschrijve1 — Wed, 06 Aug 2014 15:11:35 GMT

I created a pull request to add some info on this in the User Guide: https://github.com/Activiti/Activiti/pull/354

Re: Identity Service for Process Engine Only - No Explorer

taruntyagi — Thu, 07 Aug 2014 07:49:00 GMT

Thanks frederikheremans, this really helps and actually clarified a wrong assumption. It is clear to me that Identity Service will be used to fetch groups of a user when we search tasks for a 'candidate user'. This is not used, if we are searching for assigned tasks. Makes sense as well.

Thanks to aschrijver, I was actually making the mistake you mentioned. My Factory class was returning the type as MyCustomUser / Group class. I did debug until to look at all session factories and thought it did not look OK. But the code for custom identityservice was taken from a blog page , and I thought that's the way it should be done

With the change you suggested, my identity service is getting called and working as expected.

Thanks for your help.

Regards
Tarun

Re: Identity Service for Process Engine Only - No Explorer

edgarjoao — Fri, 06 Nov 2015 06:29:21 GMT