On Sun, 2023-04-30 at 15:58 +0930, Tim via users wrote:
> Tim:
> > > A password mismatch ought to be authorisation failure (you are
> > > not
> > > authorised). An authentication failure would be some other
> > > problem
> > > (it can't do the authentication).
>
>
> Patrick O'Callaghan:
> > I do
Tim:
>> A password mismatch ought to be authorisation failure (you are not
>> authorised). An authentication failure would be some other problem
>> (it can't do the authentication).
Patrick O'Callaghan:
> I don't think so. Authentication is about identifying the user,
> authorisation is deciding
On Sun, 2023-04-30 at 06:10 +0930, Tim via users wrote:
> On Sat, 2023-04-29 at 17:39 +0100, Patrick O'Callaghan wrote:
> > In *some" cases, usernames are added to the password file, and the
> > password verifies correctly (using 'htppasswd -v ...'), but Apache
> > still throws an error, e.g.:
> >
On Sat, 2023-04-29 at 17:39 +0100, Patrick O'Callaghan wrote:
> In *some" cases, usernames are added to the password file, and the
> password verifies correctly (using 'htppasswd -v ...'), but Apache
> still throws an error, e.g.:
>
> [Sat Apr 29 17:12:10.790251 2023] [authz_core:error] [pid 17622
On Sat, 2023-04-29 at 17:39 +0100, Patrick O'Callaghan wrote:
> In *some" cases, usernames are added to the password file, and the
> password verifies correctly (using 'htppasswd -v ...'), but Apache
> still throws an error, e.g.:
>
> [Sat Apr 29 17:12:10.790251 2023] [authz_core:error] [pid 17622
My small web server is now mostly working, but I'm having a very
strange problem. I can *usually* add user accounts from the Shell using
htpasswd, and they can log in successfully.
Except when I can't.
In *some" cases, usernames are added to the password file, and the
password verifies correctly
