Support for HTTP Basic Authentication when registering templates or ISOs from HTTPS URLs

Offen
  • Stimmt etwas nicht?
#14,461 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
backend-api-design, cloud

Rechercherichtung

Start by tracing the template and ISO URL registration flow through the API, UI, and secondary storage download path; the issue names HttpTemplateDownloader and DownloadManagerImpl in its logs. Find where download credentials are configured and how registration parameters reach that code. Done means valid credentials can be supplied for HTTPS Basic Authentication and private artifacts download successfully.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

component:api component:UI type:enhancement
ISSUE TYPE
  • Feature Idea
  • Enhancement Request
COMPONENT NAME
Templates / ISOs / URL-based registration / Secondary Storage
CLOUDSTACK VERSION
All versions
CONFIGURATION
N/A
OS / ENVIRONMENT
N/A
SUMMARY

The CloudStack template and ISO registration flow supports downloads from remote URLs, but it does not currently provide a mechanism to authenticate to protected HTTPS endpoints that require HTTP Basic Authentication.

This limits the ability to register templates and ISOs from secure artifact repositories such as JFrog Artifactory, Nexus, or similar services that require a username and password before the artifact can be retrieved.

DESCRIPTION

CloudStack should support authenticated URL-based downloads when registering templates or ISOs. In particular, the registration flow should allow a user to provide credentials for HTTPS endpoints that require HTTP Basic Authentication.

At present, the system does not expose a standard mechanism to pass a username and password during URL-based template/ISO registration. As a result, authenticated remote sources cannot be used directly and users are forced to make those resources publicly accessible or use unsupported external workarounds.

This is a common requirement in enterprise environments where artifacts are stored in private repositories and are exposed only through authenticated HTTP endpoints.

EXPECTED RESULTS

The CloudStack UI and API should allow template and ISO registration from HTTPS URLs that require HTTP Basic Authentication.

The feature should support providing:

  • username
  • password
  • optional authentication metadata if required by the backend

and should permit successful download of the artifact when valid credentials are supplied.

ACTUAL RESULTS

The download fails because CloudStack does not provide a way to pass credentials to the HTTP endpoint. The operation typically fails with authentication errors such as HTTP 401 Unauthorized or equivalent download failures.

2026-10-21T17:47:05,415 INFO  [storage.template.HttpTemplateDownloader] (AgentRequest-Handler-5:[]) No credentials configured for host=artifact.it.com:443

2026-10-21T17:47:06,414 INFO  [storage.template.DownloadManagerImpl] (pool-2-thread-2:[]) Download Completion for jobId: 0184fd4a-f8a6-4016-8430-67ae5ba23a25, status=UNRECOVERABLE_ERROR

2026-10-21T17:47:06,433 INFO  [storage.template.DownloadManagerImpl] (pool-2-thread-2:[]) local: /mnt/SecStorage/233b2e1f-c329-39f4-83ae-6ed1f66f22bd/template/tmpl/2/338/dnld680537437357276481tmp_, bytes=(0 bytes) 0, error= HTTP Server returned 401 (expected 200 OK) , pct=0
PROPOSED SOLUTION

Add support for HTTP Basic Authentication in the template/ISO URL registration flow.

The solution may include:

  • username and password fields in the UI
  • API parameters for authenticated downloads
  • validation of credentials during the source fetch
  • support for private repositories such as JFrog Artifactory
IMPACT

This feature is required for secure enterprise deployment practices. It enables CloudStack to consume artifacts from private, authenticated repositories without exposing those artifacts publicly or relying on unsupported manual workarounds.

Vorherrschende Sprache
Java
Sterne
3.1k
Forks
1.4k
Ø Merge
7 T. 16 Std.
Gemergte PRs (30 T.)
15

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus apache/cloudstack

Alle Issues in apache/cloudstack

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.