Anything on the long-term roadmap for this to be setup, similar to how both can use Laserfiche Cloud's web services?

Import Agent is not something I would ever expect to be running externally because it is more for "pulling" things into Laserfiche and there are many ways to bring the files in while still hosting it on the inside.

When we need to allow documents to be imported from external sources, we create a path that is accessible via VPN, trust relationships, FTP, etc. and monitor those folders with Import Agent running within our network.

Basically, we only ever run Import Agent on the receiving end, and when we need to pull things in from the outside, we set up a "drop zone" rather than putting the entire import agent on the outside.

Jason, while I agree with you , we have tried these options but the customer will not accept any.  As Laserfiche has set up ImportAgent to be installed locally and work with their Cloud setup, I was hoping they would do something similar for their on-prem customers.  Their scan client for the WebClient allows someone to scan a document locally and then pass it into Laserfiche via the WebClient, why not allow ImportAgent at least the option to do the same?

It is not a trivial technical task. The Scanning -> Web Client mechanism is a user-interactive one that relies on browser sessions and the WebTools Agent utility to act as an authentication cache. Import Agent currently doesn't even have the concept of a browser (which it would have to run headless), and has no integration points with WebTools Agent. 

Laserfiche Snapshot, which is at least user interactive and has a common enough legitimate use case for wanting to go through Web Client, still doesn't support that due to technical challenges.

Import Agent with Laserfiche Cloud does not relay through Web Client. It directly connects to a Cloud endpoint that's the logical equivalent of a self-hosted Laserfiche Server. Outside of added compatibility with Cloud's ACS authentication system, it fundamentally works the same way as on-prem.

This is the first time I've heard of anyone wanting to do that with Import Agent, and the use case, to be generous, is niche. Speaking plainly, it would not pass a feature request review, especially given the implementation effort and wide availability of viable workarounds to address the use case.

@████████'s approach here is correct. Host Import Agent on the same internal network as Laserfiche Server. Figure out a way to copy/move content from the external file location to the internal one. There are tons of options for this. Or propose something like Azure Files where both sides can have authenticated access to a hosted file share.

Thanks for all of the suggestions.  I figured it was a tough ask but had to give it a try based on the unique requirements by this customer.  We've had the discussions for all of these possible workarounds (plus a hundred others) but no luck in getting them approved.  At this point we are looking at the Laserfiche API to bring in the documents.  I really do appreciate all of the ideas!