Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for authenticated apt repos #632

Open
pandel opened this issue Jan 10, 2025 · 3 comments
Open

Support for authenticated apt repos #632

pandel opened this issue Jan 10, 2025 · 3 comments

Comments

@pandel
Copy link

pandel commented Jan 10, 2025

Hi!

Some of my hosts use a repository for which authentication is required. The authentication is done via a configuration file under /etc/apt/auth.conf.d on the host itself.

Patchman reports this repo as Repositories where all Mirrors are failing and that is correct from patchman's point of view, because patchman is not allowed to download the repo list.

So, how do I get the data from the restricted repo into patchman? Can I provide patchman with the necessary authentication data somehow?

Regards,
Holger

@pandel pandel changed the title Repository with authentication fails Download of content of repository with authentication fails Jan 10, 2025
@furlongm
Copy link
Owner

We don't (yet!) support authenticated apt repos.

A workaround may be to set the clients to report local updates?

@furlongm furlongm changed the title Download of content of repository with authentication fails Support for authenticated apt repos Jan 10, 2025
@pandel
Copy link
Author

pandel commented Jan 10, 2025

Ah! Do you mean the -u parameter of patchman-client? I will try that when I am back in the office...

@pandel
Copy link
Author

pandel commented Jan 13, 2025

So, I tried -u, but that doesn't change the message on the dashboard. The available updates are being still reported though. I can live with that, although it will be nice if authenticated repos are supported in the future :-) many thanks!

@pandel pandel closed this as completed Jan 13, 2025
@furlongm furlongm reopened this Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants