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

Abierto
  • ¿Algo no está bien?
#14,461 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java
Área
backend-api-design, cloud

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Java
Estrellas
3.1k
Forks
1.4k
Merge medio
7 d 16 h
PR fusionados (30 d)
15

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de apache/cloudstack

Todos los issues de apache/cloudstack

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.