We have a similar requirement, and have extended the org.activiti.engine.impl.persistence.entity.UserManager, using our Spring services to fetch users, and transform them to an Activiti User. We also needed to create a custom SessionFactory (CustomUserManagerFactory) which is a factory for our cutom UserManager. The same pattern can be used to provide custom groups if needed. Here is a sample of the classes:
@Service
class CustomUserManagerFactory implements SessionFactory {
@Autowired
CustomUserManager customUserManager;
public Class<?> getSessionType() {
// original UserManager
return org.activiti.engine.impl.persistence.entity.UserManager.class;
}
public Session openSession() {
// Customized UserManger extended from org.activiti.engine.impl.persistence.entity.UserManager
return customUserManager;
}
}
@Component
public class CustomUserManager extends UserManager {
@Autowired
private UserService userService;
@Override
public UserEntity findUserById(String username) {
Assert.notNull(username, "username must not be null");
com.our.app.model.User user = getUserService().findUserByusername(username);
return toActivitiUser(user);
}
….
}
They can then be wired into spring:
<bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
<property name="databaseType" value="${activiti.databaseType}" />
<property name="dataSource" ref="dataSource" />
<property name="transactionManager" ref="transactionManager" />
<property name="databaseSchemaUpdate" value="${activiti.databaseSchemaUpdate}" />
<property name="jobExecutorActivate" value="${activiti.jobExecutorActivate}" />
<property name="customSessionFactories">
<list>
<bean class="com.your.app.CustomUserManagerFactory" />
<bean class="com.your.app.CUstomGroupManagerFactory" />
</list>
</property>
</bean>
