Adam Laurie wrote:
>
> FakeBasicAuth will look in your authfile for an entry matching the X509
> of the cert that's requesting the connection. It needs to have an entry
> like this:
This wasn'T the original problem. He doesn't know about client authentication.
He was surprised that BasicAuth didn'T work anymore.
According to my expirience this may happen when FakeBasicAuth is set.
(although other possibilities exist for sure)
> /O=Their Company/CN=A
> Punter/Email=punter@gosh.look.at.this.internet.thingy:xxj31ZMTZzkVA
>
> For each certificate that's allowed to connect.
>
> The 'xxj31ZMTZzkVA' password is a default built in at compile time, and
> is the same for every user. If it's set up correctly, you will not see
> the Basic Auth login dialogue at all.
>
> cheers,
> Adam
>
> Holger Reif wrote:
> >
> > > I'm using apache since a long time, and I never had problems with
> > > User authentication for special directorys.
> > >
> > > After updating to apache SSL, I always get an authentication
> > > error back.
> >
> > Perhaps take the FakeBasicAuth option out of the config?
--
read you later - Holger Reif
------------------------------------ Signaturprojekt Deutsche Einheit
TU Ilmenau - Informatik - Telematik (Verdamp lang her)
Reif@PrakInf.TU-Ilmenau.DE Alt wie ein Baum werden, um ueber
Remus.PrakInf.TU-Ilmenau.DE/Reif/ alle 7 Bruecken gehen zu koennen