topic Login problem: The security token could not be authenticated in Alfresco Archive

Login problem: The security token could not be authenticated

fluca1978 — Mon, 28 Mar 2011 08:30:56 GMT

Hi all,I'm using a web service to manage documents in an Alfresco share. The application uses JSF and there is a component (a singleton) that manages the access to the repository, so that different users are all going thru the same component instance to access the share. Such component performs an a

Re: Login problem: The security token could not be authenticated

fluca1978 — Tue, 29 Mar 2011 08:14:15 GMT

I changed the call to the startSession in order to include a timeout, and the errors are still there but with a less frequency:


AuthenticationUtils.startSession( configuration.getUsername(),
                  configuration.getPassword(),
                  360000
            );
‍‍‍‍‍‍

However, under some circumstances the problem still arises. Is there anybody that can suggest a solution?

Thanks.

Re: Login problem: The security token could not be authenticated

fluca1978 — Fri, 01 Apr 2011 10:34:13 GMT

At the moment I forced the application to do a full login-logout cycle for every main operation done against Alfresco. I mean, for instance, that for searching a document I do login-search-logout, while to download a found document I do again login-download-logout. This makes the application running slower but I hope will fix the problem.
If anyone has other ideas please advice.

Re: Login problem: The security token could not be authenticated

npasquetto — Thu, 30 Jan 2014 14:01:49 GMT

Hi fluca1978, have you resolved this issue? I've got the same behaviour on a cluster based on Alfresco 3.2

The full login-logout cycle has resolved the problem?

Re: Login problem: The security token could not be authenticated

scouil — Thu, 30 Jan 2014 17:24:21 GMT

Hi,

You may want to review your cluster configuration.
If the sessions are not properly replicated, then as long as your requests are handled by the same server you will be fine but as soon as it will end up on another server in the cluster, that server will not recognise the session as valid.