Hello,
Please add support for Basic Authentication on the client side when RepoManager synchronizes packages from remote repositories
At the moment, this is needed for cases where the source repository is protected by Basic Auth and RepoManager should authenticate itself while downloading/syncing packages.
Expected behavior
RepoManager should allow configuring:
- remote repository URL
- Basic Auth username
- Basic Auth password
and use these credentials when synchronizing packages from the remote repository.
Current workaround
Right now, I embed the Basic Auth credentials directly in the repository URL, but this is not a good security practice and should be avoided.
Why this is needed
Many internal and external package repositories are protected by Basic Auth.
Without client-side Basic Auth support, RepoManager cannot sync from such repositories directly.
Suggested scope
Support Basic Auth for:
- RPM repository sync
- DEB repository sync
- any other remote repository types supported by RepoManager
Thank you.
Hello,
Please add support for Basic Authentication on the client side when RepoManager synchronizes packages from remote repositories
At the moment, this is needed for cases where the source repository is protected by Basic Auth and RepoManager should authenticate itself while downloading/syncing packages.
Expected behavior
RepoManager should allow configuring:
and use these credentials when synchronizing packages from the remote repository.
Current workaround
Right now, I embed the Basic Auth credentials directly in the repository URL, but this is not a good security practice and should be avoided.
Why this is needed
Many internal and external package repositories are protected by Basic Auth.
Without client-side Basic Auth support, RepoManager cannot sync from such repositories directly.
Suggested scope
Support Basic Auth for:
Thank you.