Bug report #14414
Updated by Jürgen Fischer over 6 years ago
I added authentication system support to the plugin manager/installer manger/installer in commit:36e7026.
That works if the entire plugin repo endpoint is authenticated, but fails if just the download of the plugin requires authentication. In the latter case, plugins are listed in the plugin manager via non-authenticated calls to *http[s]://my.pluginrepo.tld/plugins.xml*, however the actual download of the plugin's ZIP archive is from an HTTP[S] BASIC authentication directory, e.g. *http[s]://my.pluginrepo.tld/packages/plugin.zip*.
Note the connection does still work, i.e. prompting for the HTTP Basic auth credentials, though fails to use any predefined authentication system configuration.
The attached patch fixes this.
That works if the entire plugin repo endpoint is authenticated, but fails if just the download of the plugin requires authentication. In the latter case, plugins are listed in the plugin manager via non-authenticated calls to *http[s]://my.pluginrepo.tld/plugins.xml*, however the actual download of the plugin's ZIP archive is from an HTTP[S] BASIC authentication directory, e.g. *http[s]://my.pluginrepo.tld/packages/plugin.zip*.
Note the connection does still work, i.e. prompting for the HTTP Basic auth credentials, though fails to use any predefined authentication system configuration.
The attached patch fixes this.