I’ve written a custom immediate delivery service. It worked fine in my development environment, with one exception: it was being called remotely even though it was local. This was failing because the TN client apparently didn’t authenticate, so the call to the service failed with an authentication required exception. To get around this, I set the ACL on the immediate delivery service to Anonymous. The problem stopped and the service worked fine.
I’ve now moved it to our STAGING environment. This is on the same server but a different port (6666). When I attempt delivery now, it is doing a remote call back to my DEVELOPMENT instance. I went back to my DEVELOPMENT instance and set the ACL on the service back to default. Then I went back to my STAGING instance and reprocessed, and sure enough it failed with that authentication problem (that would only happen if it were trying to call into the development instance).
When I get the info about the registered service, there is a value of “local” that is “true”. And there is no remote information associated with the registration.
I’m on 8.2.0.
Any help would be appreciated ASAP! (I also put a ticket in with SAG)