topic Re: Separating out User Management in Alfresco Archive

Separating out User Management

agarwalk — Tue, 20 Sep 2011 09:11:55 GMT

Hi, I have a centralized user management system which I want to use in my application in which Activiti is used as a process management tool. I dont want to have the pain of syncing the users with activiti user database. If I see the tasks APIs in Activiti, it doesn't validate the users are th

Re: Separating out User Management

rkroll — Wed, 16 Nov 2011 20:55:46 GMT

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>

Re: Separating out User Management

meyerd — Fri, 18 Nov 2011 08:20:32 GMT

To answer the initial question:
You can use activiti without the internal identity management. So assigning a user task to any "string" is fine and one of the intended ways to use activiti.

Plugging into activiti identity management (as the previous post shows) is necessary if you want users from an external source to be able to log into the activiti explorer. But if you are just embedding the engine, this is not required.

Re: Separating out User Management

lykm02 — Tue, 27 Dec 2011 04:10:17 GMT

To answer the initial question:
You can use activiti without the internal identity management. So assigning a user task to any "string" is fine and one of the intended ways to use activiti.

It's acceptable for me.

Plugging into activiti identity management (as the previous post shows) is necessary if you want users from an external source to be able to log into the activiti explorer.

But if you are just embedding the engine, this is not required.

I am confused with the conclusion. So, could you show some sample ? Or more detail description?