I see that you are using external forms “jsf”. which means the current authentication should be set before starting the process or otherwise the engine will not know the authenticated user who starts the process.
For my understanding: I thought, the process definition key is generated from the engine, when I choose a process name from the “start process” link in tasklist and click start.
The process instance is generated when I call camundaTaskForm.completeProcessInstanceForm() by sending the form. Is that right?
So where is the point that I have to call a method which contarns the code you showed me?
Authentication should be handled by your application then passed to camunda using the above call. You can do that using servlet filter where you call the above setAuthentication() method “The filter should be mapped to the URL pattern of your jsf task forms”. That way the current authentication would be available in the current thread where jsf task form is running.
I found my post from last year. Is there a way to add a servlet filter to the camunda tasklist? How can I add it? I know how to add it to my jsf application but not how to add it to the camunda tasklist.
If I would have an own login page I could read out the user. Then I could pass it to camunda (therefore I need your help: how can I pass it to camunda? How can I programmatically login to camunda tasklist?)
I want to avoid to implement an own tasklist.
Thank you again for your help
What I had pointed out in the above post is to define servlet filter in the JSF external application. And this solution would be a good option in case both tasklist and JSF external application are configured to run in Single Sign On mode.