Customer wants to POST from their webserver directly to Workflow webservices. How can we pass credentials, or simply force credentials if it is coming from a known IP address?

I reviewed this article:

https://answers.laserfiche.com/questions/55829/How-to-convert-PDF-Byte-Array-into-PDF-document

The suggested solution has a really great SDK sample script to use inside a workflow rule (Thank you for sharing with everyone).  I built up a workflow rule with an input parameter to feed the SDK script.  I then created a little Visual Studio 2010 .NET project to feed the workflow web service following this LF Support Article (and here too, thanks again for sharing with everyone):

https://support.laserfiche.com/GetFileRepositoryEntry.aspx?id=2732&mode=download

I was able to modify the workflow SDK script inside the workflow rule slightly to accommodate the Byte "stream" (The Base64 Encoded string) to use the workflow input parameter and create a PDF inside Laserfiche from the .NET project following the support article.  Way Cool!

I had to enable Windows Authentication and HTTPActivation as suggested from this answer to get the .NET project to work at all:

https://answers.laserfiche.com/questions/54974/Configuring-the-the-Workflow-Web-Service-prior-to-consuming-it

I know IIS can be setup to allow a specific IP address, Network range, or even Domain name. 

The little VS2010 .NET project will only work though when it is executed directly from the workflow server itself.  I am wondering how to change the authentication on the Workflow Web Service to allow a specific IP address to call the workflow web service from another web server, or let the Visual Studio 2010 .NET Project run on a machine other than the workflow server itself.  When I enable Anonymous Authentication and add a local IP subnet as allowed, the .NET project encounters the security exception requesting NTLM or Windows Authentication.