We're investigating ways to secure our installation/update files using Advanced Installer. We are going to be hosting our initial installer in an S3 bucket that users will download via an AWS S3 Signed Url. I'd like to use the same sort of security during updates, but I'm only seeing the option of username:password as part of the "Updates configuration file URL" like so:
Code: Select all
http://<username>:<pwd>@www.myurl.com/<client>/downloads/setup.exe
Is this the ONLY means by which the updater process can access secure files?
I have an idea I wanted to run by support.... Could I change the configuration file URL to access an API that would serve up a configuration file that is constructed at request time? The API would be responsible for generating the signed S3 url and returning it inside the config file.
Thanks in advance.