| JakeJim 2005-03-08, 2:47 am |
| I am having problems with htaccess password protection too.
I imported a htaccess file into my frontpage and then onto my site.
The htaccess is protecting a members area and it works.
But once I installed it now I can't use frontpage to work/edit/publish my
members area because a password box pops up and my password to my cpanel/file
manager on the server does not work.
I have to disable my password protection in order to work on my members area.
My webhost also told me the problem is frontpage 2003 and there is nothing
that can be done.
I was told to make a subweb for the members area but it already was a subweb
and still no cigar. There's got to be other people out there like us, I
don't want to waste 200+ dollars that I could of used towards buying
dreamweaver. ANY IDEAS?
"Thomas T" wrote:
> I'm using FP 2002 extensions on an Apache server through
> a hosting company. I understand that there are some
> limitations with FPE in a unix environment, however I
> cannot find anything about the following:
>
> The website in question contains a password protected sub
> web (anonymous browsing disabled, using unique
> permissions).
>
> In setting up new users, the send an invitation wizard on
> the Permissions Administration page seems to function
> properly, allowing me to enter in an e-mail addresss,
> account name, full name, personal greeting, and role
> assignment (defaults to browser). It then sends an e-
> mail with the userid and system generated password to the
> recipient. The e-mail contains a link to a page on the
> site located in a subdirectory named
> _vti_bin/_vti_aut/passwd.htm.
>
> The problem exists when any recipient links to this page,
> it is immediately requiring a userid and password to gain
> access. The only userid and password that it is
> accepting is an administrator userid and password. Once
> into the page, everything else functions properly, and
> the user can change the password.
>
> From my perspective, I can't give out administrator
> permission to general users. I can't believe that this
> is functioning properly since it would be a violation of
> every security best practice to not allow a user to have
> privacy on their password.
>
> What the hosting company is telling me is that the
> htaccess file is limiting access to the page, thus not
> allowing people with browser level access to change their
> own passwords.
>
> Is this a limitation of FP Extensions 2002 installed in a
> unix environment, or is this an configuration problem on
> their end, or do I have a misunderstanding of the
> functionality and how to use it?
>
> I need enough information to communicate this to the
> hosting company.
>
> They are looking into this problem, but their suggestion
> is to discontinue using FPE.
>
> Thanks for any assistance that you can provide.
>
|