Hi Michelle,
There are systems that allow you to authenticate a user, set a cryptographic
session cookie on the client browser and subsequently use that token to
authenticate the client sending the HTTP request. These systems also allow you
to define access control rules that depend on the user
--- Nick Owen <[EMAIL PROTECTED]> wrote:
> On 9/25/07, Michelle Konzack
> <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I have a couple of servers (currently 42
> Web-Servers et a redunant
> > PostgreSQL for AUTH) and I am trying to get a
> One-Time authentification
> > running.
> >
> > Exactly:
On 9/25/07, Michelle Konzack <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a couple of servers (currently 42 Web-Servers et a redunant
> PostgreSQL for AUTH) and I am trying to get a One-Time authentification
> running.
>
> Exactly:
>
> It should not mather on which Web-Server the $USER authentica
Michelle,
I am not an apache expert. However, it sounds like you need an actual
programming to do what you would like to do.
>From the sounds of it, you would need to have a central program which
would check authentication every time the user made a request. If the
user wasn't logged in, it wou
