topic [RESOLVED] Spring authentication issue in 5.11 in Alfresco Archive

[RESOLVED] Spring authentication issue in 5.11

aduarte — Thu, 24 Jan 2013 17:34:01 GMT

Hi everybody,I have an application based on Spring Framework/Hibernate/Vaadin, split in differents layers (Repositories, Services, Views). I've secured my services methods with @PreAuthorize annotations.I use activiti engine to automate some treatments : I design workflows with Activiti Designer Ecl

Re: [RESOLVED] Spring authentication issue in 5.11

aduarte — Thu, 24 Jan 2013 17:43:17 GMT

It is not related to the thread because if I start the process directly from my app, I still got the problem.

Thanks for helping

Re: [RESOLVED] Spring authentication issue in 5.11

frederikherema1 — Fri, 25 Jan 2013 09:22:06 GMT

Are the service-tasks asynchronous? From what I remember, the security-context is stored thread-local. So as long as the same thread is used (and context is not cleared), this should be working all the time, or am I missing something?

Re: [RESOLVED] Spring authentication issue in 5.11

aduarte — Fri, 25 Jan 2013 09:51:07 GMT

My service tasks are not asynchronous. I want to execute them in sequence. When a task is finished, the next starts.
I read some thing about thread-local security context and I tried to fix my issue by setting the context in INHERITABLETHREADLOCAL strategy mode but nothing changed.

Some news about my investigations:
I came back to activiti 5.10 in my pom.xml, and replace my workflow by an old version => everything is ok.
But when I open the workflow with the designer (5.11) and just move the startevent 1 pixel to the left => the problem came back.
I compared the two files opening them in xml format and I see some changes:
isExecutable="true" has been added by the designer and "manualTask" has been replaced by "task"

Re: [RESOLVED] Spring authentication issue in 5.11

frederikherema1 — Fri, 25 Jan 2013 10:32:49 GMT

That could explain a lot… a manual-task will behave differently than a regular task? Is there a reason why you're using manual-tasks instead of user task or service task?

Re: [RESOLVED] Spring authentication issue in 5.11

aduarte — Fri, 25 Jan 2013 10:45:21 GMT

I put a manualTask at the begin of all my processes in order to persist the process in the database because I read that when you start a process it is not persisted until a manualTask/userTask… and endEvent I imagine.

But calls to my application services are done in service tasks.

This is the beginning of my process to explain that : http://hpics.li/c3a7c34

Re: [RESOLVED] Spring authentication issue in 5.11

frederikherema1 — Fri, 25 Jan 2013 10:49:24 GMT


/**
 * Implementation of the BPMN 2.0 'manual task': a task that is external to the
 * BPMS and to which there is no reference to IT systems whatsoever.
 * 
 * Given this definition, this activity will behave simply as a pass-though step
 * in the process.
 * 
 * @author Joram Barrez
 */

Only wait-states will persist the process, the manual-task will just passthrough, not persisting… Not really sure why you want your process persisted, while it still could be rolled-back by an error in the subsequent service-tasks??

Re: [RESOLVED] Spring authentication issue in 5.11

aduarte — Fri, 25 Jan 2013 11:25:36 GMT

Ok, I think I misread something. Removing the manual task at the beginning fixes my issue.
I need to make some tests because I think I have put that manual task to fix a problem about getting some process variables in some specific case (it has been a long time and don't remember exactly the problem I was facing but someone told me to put the manual task as a trick).

Thanks a lot for your help. I test if everything is ok and put the topic as resolved.