I’ve been using apt-cacher-ng inside a sys-cacher, as I know several of you do as well. One issue I have is with the AdminAuth setting (as seen in ben-grande’s implementation — when it is set, the admin portal does not offer me the opportunity to supply a username and password, but gives me a 401 instead. I’m aware the information is supposed to be in the Authorization header, but is there a way to supply this when using the browser?
I dont use the qusal implementation.
Setting access controls is a standard part of apt-cacher-ng - I tend
not to do it in Qubes.
You should be able to access the report page unhindered, but be prompted
for name/password when using admin functions - what browser are you
using?
I never presume to speak for the Qubes team.
When I comment in the Forum I speak for myself.
I’m using trivalent, with celenity/Titanium policies applied. (I’ll have to see if the policies are involved, but I would be surprised.) What I observe is that I am able to access the report page unhindered, but I get served a “Not Authorized” page when I click on any of the admin functions.
Edit: turns out the policies were the issue.