Tinyproxy releases supporting BasicAuth can require a login before permitting proxy access. A configuration entry looks like this:

BasicAuth alex replace_with_a_private_password

Use the manual shipped with your release. The Tinyproxy 1.11.1 parser already includes BasicAuth, while older discussions can predate the feature.

Protect the configuration file: this entry contains a usable password. The daemon's operating-system User setting selects its process account, not a proxy login.

Client access and transport

Retain the intended Allow and Deny rules alongside authentication. Tinyproxy client-access settings remain separate from the account check. They restrict eligible clients; BasicAuth checks their credentials.

HTTP Basic authentication provides no transport encryption. The destination's HTTPS tunnel cannot protect a login already exchanged with a cleartext proxy. An SSH tunnel to a loopback-only Tinyproxy is one possible protected path.

If the browser keeps prompting, compare the supplied credentials with the effective configuration and confirm the running version supports the directive.

Mikanda mikatakata