I am developing a web application that uses an external LDAP server for login. Once logged-in, I would be performing some workflow process using Flowable REST. I have manually created some users and user groups in Flowable IDM and provided them access to REST APIs. Now I am not okay with using both LDAP server and Flowable IDM.
Can I use only Flowable IDM for both login and workflow process and get rid of the LDAP server completely? Is that possible in Flowable IDM?
The default IDM implementation is simple and typically won’t be used for real deployments (In the upcoming 6.6.0 release, the way this can be configured will simplified). What is your use case for adding LDAP to the REST application? One option could be to do the calls with a technical user in the requests, and passing the user/group info in the REST calls without having to need to hook up LDAP.
I am developing a web application from scratch which uses flowable for few workflow use cases. I have planned to store users information in Apache Directory Service, where user registration and login authentication are performed. Instead, If I store the user information in Flowable IDM, can I use this for performing user registration and login authentication? Can Flowable IDM be used as a directory service in this case?
Basically I wanted to know if Flowable IDM can be a potential production grade substitute of other Directory Service providers like ApacheDS, Microsoft Active Directory.