nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Separating out User Management

agarwalk

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 there in Activiti DB or not.

   This means I can assign a task to any user Name / group (even when these are not present in Activiti).

   I am using Spring for all my business logic and all the security related activities are hanled by Spring itself.

   Just wanted to confirm if this is valid or not?? Can I use activiti without using its user management portion.

   I understand for logging purpose I can set IdentityService.setAuthenticarId() externally.

   Request thoughts on this..

Thanks in advance

Find more posts tagged with

Comments

rkroll

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:

<br>@Service<br>class CustomUserManagerFactory implements SessionFactory {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; @Autowired<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CustomUserManager customUserManager;<br><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; public Class<?> getSessionType() {<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; // original UserManager<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; return org.activiti.engine.impl.persistence.entity.UserManager.class;<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; }<br><br> public Session openSession() {<br>&nbsp; // Customized UserManger extended from org.activiti.engine.impl.persistence.entity.UserManager<br>&nbsp; return customUserManager;<br> }<br>}<br><br><br>@Component<br>public class CustomUserManager extends UserManager {<br><br> @Autowired<br> private UserService userService;<br><br> @Override<br> public UserEntity findUserById(String username) {<br>&nbsp; Assert.notNull(username, "username must not be null");<br>&nbsp; com.our.app.model.User user = getUserService().findUserByusername(username);<br>&nbsp; return toActivitiUser(user);<br> }<br><br>&hellip;.<br><br>}<br>

They can then be wired into spring:

<br><bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration"><br>&nbsp; <property name="databaseType" value="${activiti.databaseType}" /><br>&nbsp; <property name="dataSource" ref="dataSource" /><br>&nbsp; <property name="transactionManager" ref="transactionManager" /><br>&nbsp; <property name="databaseSchemaUpdate" value="${activiti.databaseSchemaUpdate}" /><br>&nbsp; <property name="jobExecutorActivate" value="${activiti.jobExecutorActivate}" /><br>&nbsp; <br>&nbsp; <property name="customSessionFactories"><br>&nbsp;&nbsp; <list><br>&nbsp;&nbsp;&nbsp; <bean class="com.your.app.CustomUserManagerFactory" /><br>&nbsp;&nbsp;&nbsp; <bean class="com.your.app.CUstomGroupManagerFactory" /><br>&nbsp;&nbsp; </list><br>&nbsp; </property><br> </bean><br>

meyerd

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.

lykm02

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?