Kelly Wright (kwright@buz.net)
BuzNet Communications (www.buz.net)
972-644-0440
----------
> From: Sam Akhtar <srakhtar@ibisnet.net>
> To: emerald@iea.com
> Subject: Re: IIS3, FrontPage, and Emerald
> Date: Monday, February 17, 1997 1:42 PM
>
> > FrontPage seems to want me to maintain an NT User account for each user
> > that will be publishing via FrontPage, and seems to grant access on a
> > virtual server basis.
> Yes; we've run into the same.
>
> > Well, if I have "http://users.domain.com" as a virtual server, and all
> > users homepages are under that virtual server, how can I have FrontPage
> > authenticate and protect the security of each users' home page, based
on
> > the EMERALD account data (so I don't have to replicate Emerald's data
in
> > the NT User Manager)?
> Insofar as we've found, this is a limitation with FrontPage. You can
only
> go down one level for subwebs and you have to have a record in your NT
ACL
> for that user... unless we're missing something horribly.
> So for example, to have users off of your home domain (domain.com/user/)
> you have to have a record for user (matching it to his RADIUS id\pwd
> simplifies things) and have to have it set up as follows:
>
> \wwwroot\user\
>
> Where wwwroot is the real root of your virtual server (er, did that make
> any sense? :) )
>
> Here's hoping something more reasonable works out with Membership
> server...
>
>
> Sam Akhtar Operations & Engineering
> IBIS, Inc. http://www.ibisnet.net/
> NT - ISP FrontPage, ASP, PERL, Java... and more!
> "We give good web..." (SM)
> -
> Emerald Mailing list (emerald@iea.com)