Issue with Remote file import after washington upgrade

[Sangeetha Harin]

Hi Everyone, 

We are using Remote file import to fetch the csv file from Mid-server and processing the record to update user table. It stopped working after washington upgrade. Getting the below error. 

var remoteFileImport = new CSMIDServerRemoteFileImport();

remoteFileImport.getRemoteFileAndUploadToInstance()

Root cause of JavaScriptException: java.lang.IllegalAccessException

Any lead will be really helpful. 

Thanks

[davidpiper]

Given how much of a bad idea ALL-UNNAMED is, I think it's not a bad idea to let this cat out of the bag:
The StreamPipeline probe has existed since at least 2015, and can pull files from the mid server disk, and put them into attachments on records, as used by at least the HR Employee Document Management bulk import feature:

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0727132#mcetoc_1g24h52d32o

It's like an Export Set which also uses StreamPipeline (and there is a post around here somewhere on reverse engineering that), but using it in the other direction.

The MID Server login user would need ACLs for the record table and attachments for that table. Allowed file extensions, Max attachment size properties need taking into account, etc. but in theory that's a supported alternative.  Try and avoid weird characters in filenames though.

[MortenPettersen]

At my previous company we ended up replacing the Remote file import solution with a File Transfer software that another team was offering internally as a service. This software would move the files we needed into a SFTP Server and we used the SFTP Spoke in Integration Hub to get the files from there and attach them to a Data Source []sys_data_source] record for further processing by the ServiceNow instance.