The way I like to do it is to use a LDAP server for authentication and
entitlement. In addition to both username and password being stored, you
can create attributes that will allow you to define the level of access for
each user.
Also, with a centralized LDAP service, all your web servers are a
Joe Schulman wrote:
>
> Hey~
> This is mainly a question directed to those with experience in this
> sort of thing.
>
> In general, how should one go about authenticating a user and then
> allowing them to view separate pages under that particular login?
hi joe
if you're running apache and m
> "P" == P lerenard <[EMAIL PROTECTED]> writes:
P> on my side I just check the ip address of the host which must match.
No, an IP address is not a user. An AOL user changes IP addresses
on each hit, even within the images on a given page. A corporate
user behind a firewall shares their app
bj,
on my side I just check the ip address of the host which must match.
yes somebody can change the ip address to match the ones with the access,
but the network is not going to like that.
load-balancing but i'm not sure.
Pierre
>From: "Joe Schulman" <[EMAIL PROTECTED]>
>To: "Beginners-Cgi" <
Well, the unix way is ask for a string, hash a string, on return, ask
again, hash again, compare...
__END__
=sincerely, eduard grinvald
=email: [EMAIL PROTECTED]
=dev-email: [EMAIL PROTECTED]
=dev-site: r-x-linux.sourceforge.net
=icq: 114099136
=PGP
-BEGIN PGP PUBLIC KEY BLOCK-
Versio
On Wed, 6 Jun 2001, Joe Schulman wrote:
> This is mainly a question directed to those with experience in this sort of thing.
>
> In general, how should one go about authenticating a user and then allowing them to
>view separate pages under that particular login?
>
> I know that cookies aren't 10
