Sometimes the save method takes an admin user as current user

[joebordes]

It is rather odd as the application usually does try to keep the user connected in order to maintain that history information. That said I am sure that there are places where we check for the current_user variable and if it is not set we will pick the first admin user we find which would adapt to the case you describe.

Does this happen only with the custom webservice? Can you reproduce the issue consistently?