Super is not proxy-aware

[Sot3]

If you run Super behind a proxy server, the installation of IBM Notifier fails, and the download of the SOFA feed fails.

[Sot3]

To be more specific, running Super from Jamf fails because there is no HTTP[S]_PROXY variable available in the environment.

[Macjutsu]

I have no plans to reasearch or directly implement proxy support in super.

That being said... it's a bash script. Feel free to find all the instances of curl and throw in your proxy settings.

Alternatley, you can pre-install IBM Notifier and allow-list (or host your own) SOFA feed URL.

I'll leave this issue open, but again, I have not plans to resolve is issue directly.

[Sot3]

Obviously I'm not excited about having to edit the curl commands in every future release of super. What can I do to help get this functionality into the script? We can't possibly be the only organization that runs it behind a proxy server, so I don't understand why this wouldn't be something you want to address.

[Macjutsu]

This is the first issue anyone has raised about HTTP proxy support.

The funtamental problem is that super is a locally stored, human readable script that can run independently in the background. Thus, the script would need to have plain-text access to your proxy authentication. There is no safe way to implement this. This is why I recommended a work arround by pre-installing the required software and allow-listing the URLs that are being called.

The MOST correct answer is to move on to a more modern method of network monitoring. Most organizations I deal with (I'm a consultant by trade) have moved away from legacy HTTP proxies. They simply aren't as capable as modern content filter providers. (see this comparison: https://support.apple.com/guide/deployment/filter-content-dep1129ff8d2/web) Further, properly implemented content filtering is completley transparent to any process or application running on the system.