We have been having a strange issue with core services. Our application uses Angular as the front end and ASP.NET for back end. The back end api service connects to Tridion using core services. The Application and Tridion core services are running in different servers.
The issue we are having is that the application when accessed locally on the servers works fine. But accessing the application remotely throws an error. This error is thrown when client.Impersonate("Windows Account") is called. The "Windows Account" is present in Tridion Users. But the same code works well when running the application locally on the server.
The application uses ApplicationPoolIdentity for Identity and uses Windows authentication.
There only time the application works remotely is when we configure Tridion Impersonation Account in Identity. If I remove the account it does not work.
Did anyone else have this issue? Any insight to this issue is appreciated.