Do we need Camunda Custom Identity Provider?

We use Camunda BPM engine as Spring Boot embedded. Authentication is done at Spring Security level. We do not use Camunda TaskList. Our application will use Camuda lib to kick off the workflow, run auto task and our application UI will let user complete human task. We do not use Camunda User/Group Table and no LDAP available. Now the question is do we need Camunda Custom Identity Provider?

I can see one scenario needs it. Camunda WebApp User Profile needs user account info after user logged in even passed through Spring Security Authenticator. What other scenarios?

If we do need Custom Identity Provider, do we need to implement all the interfaces in ReadOnlyIdentityProvider? For example, checkPassword, since we handles authentication at Spring Security level, we do not really need to implement that interface.

1 Like