I am migrating an Activiti app to use Flowable 6.0.0 and the flowable-task app frontend to execute the user tasks.
I have a couple of ServiceTasks that obtain user information from Flowable using the IdentityService. This worked fine in Activiti, but I am now having problems.
In the flowable-task app there is no IdentityService bean created and after looking a little in the source code I saw that user information is obtained using the RemoteIdmService in the flowable-ui-common package (with the actual implementation using the flowable-idm app rest api)
Is there a preferred way to use the IdentityService in the flowable-task app?
I can see Three possible solutions:
- Extend RemoteIdmService to implement IdentityService and add the corresponding REST APIs to the flowable-idm app.
- Configure an IdentityService in the flowable-task app. I guess this requires setting up an idm Engine within the flowable-task app.
- Depend the ServiceTasks directly on RemoteIdmService instead of the IdentityService. Then the ServiceTask will no longer depend on the core flowable APIs and will be specific to the flowable-task app.
Thanks for any help!