Sep 05, 2017 03:43 PM|Limbobski|LINK
ok, I read about this
The article you link to explains: "The reason the whole thing worked when I was testing it was because in my case only a single hop was involved because my web server and user agent were on the same machine.", which is why it was working on my machine.
Thanks for the information. That means I have to use a specific user to connect to the webservice and change the webservice accordingly. Right now it logs who is accessing the service etc, but this doesn't work when using the same user for everything.
Or alternatively set up the web server in question as trusted for delegation, which should allow this to work.