I work for a retail organization with multiple Jump Groups, and automating the Jump Client installer download has always been a tedious but necessary task, especially since each appliance upgrade requires redownloading the installer.
To streamline this, I developed an automated process that directly retrieved the appropriate installer from the appliance via API. This solution worked flawlessly for two years—until the 24.3.2 upgrade broke it. It appears that BeyondTrust modified the schema, introducing different key_info handling for MSI-based installers and, more frustratingly, removing the option to download EXE files entirely.
What’s most aggravating is that none of these API changes were documented in the change log, making it difficult to adapt. Has anyone else encountered similar challenges post-24.3.2 upgrade? If so, have you found any viable workarounds?
