# Ignition 7.9 FTP over TLS

**URL:** <https://forum.inductiveautomation.com/t/ignition-7-9-ftp-over-tls/39818>\
**Category:** Ignition\
**Created:** [October 19, 2020, 11:23pm UTC](https://forum.inductiveautomation.com/t/ignition-7-9-ftp-over-tls/39818 "2020-10-19T23:23:14Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [October 20, 2020, 2:24am UTC](https://forum.inductiveautomation.com/t/ignition-7-9-ftp-over-tls/39818/5 "2020-10-20T02:24:16Z")

</div>

> [@Kevin.Herron](#):
>
> unless you also add scripting function implementations that use the library

In a pinch, you can supply a "script" module that just has (a) public static final field(s) that is(are) set to the class(es) you need. Like this for the report module:

> [@Report with Scripted Nested Data](http://forum.inductiveautomation.com/t/report-with-scripted-nested-data/11801/7):
>
> Hey Kathy, The problem with importing across classloaders could be mitigated by placing the following in the Java class that gets loaded to [system.report](https://docs.inductiveautomation.com/display/DOC79/system.report): public static final Class\<?\> QueryResults = com.inductiveautomation.reporting.common.api.QueryResults.class; Then anyone’s scripts could do: from system.report import QueryResults Pretty please?

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-7-9-ftp-over-tls/39818)._