How do I publish subwebs to a password protected domain?

[Jennie]

Our company website has a staff area. Each staff member has a user id and
password. On the domain, the staff area folder is password protected. There
is also a folder under the staff area folder for each staff member that is
also password protected (each staff member has their own personal page from
which they download personal stuff that other staff members shouldn't have
access to).

I can not "publish" using FrontPage 2003. It repeatedly asks for a user id
and password (when it gets to the staff area folder to list the files, this
is when I get the message). When I input my user id and password, it says
that I don't have permisson to publish. I've contacted the ISP (LunarPages),
and the permissions for our domain and all sub folders is just fine. I also
tried to add the master user id and password to every single password
protected folder as a user, thinking that might make it happy (since it was
asking for the user id and password when it got to the staff area folder).
This approach didn't work.

The weird thing is, that if I remove all the password protection on the
domain end, then publish with FrontPage 2003 (including subwebs), it
publishes everything just fine. I'm just tired of having to undo, then redo
all the passwords. This is a major pain in the rear when you just need to
change a single page (there are over 40 password protected folders). I've
checked, and FrontPage extensions are installed on the main web and subwebs
(which is evident, since it will publish when the passwords are removed).

The service provider says that I need to delete the entire web from the
public html directory and publish from scratch (then re-establish all the
password protected folders, recreate all user ids and passwords etc.). This
will take at least an entire day, which I simply don't have. Certainly there
is something else that will fix this problem!

Thanks in advance.

 

[Thomas A. Rowe]

You might want to consider another approach, such as restricting access via a ASP/ASP.net with a
database instead of via the extensions/OS or looking using WSS if running on Windows 2003 Server.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Mike]

Another option would be to make each protected folder a subweb and then all
these diffrent passwords would work. I know creating a few subwebs, this
feature works the way that you are wanting it to work, but I am unaware of
the limitations of the number of subwebs that are allowed. It would seem
that there are none.

In the administration area where you assign the user name, password and
rights for each individual subweb, you can also add a user name for you that
is the same across all subwebs which will allow you to manage it. You will
have to log into the each administrative area of each subweb to set this up
and by added your account to each should allow you to manage it.

After it is setup - Add all of the different subwebs into your Trusted Sites
in Internet Explorer and then you will not be promtped for a password again
after your initial login if you check Save Password.

Each subweb session will open up in a new Frontpage instance.

Hope this helps ...

 

[Jennie]

Making each staff members folder a subweb didn't work. It made things
worse when I tried to publish and eventually locked up my computer.

This problem started then I made the "Staff Area" a subweb of our company
web site. It was necessary to do this because I wanted a completely different
set of shared borders, theme, etc. for the staff area (and I didn't want to
have to make all the buttons/menus/drop downs manually - way too many pages
and my boss is constantly having me change things around).

I never had any trouble publishing to the password protected "staff area"
directory before when the web site was just ONE site. When I changed the
"staff area" folder to a subweb, that is when the problems started. Then,
when my boss needed me to add a custom personal page for each staff member,
without anyone else being able to see it, my problems multiplied. This is why
I'm currently removing and then replacing the passwords on the folders each
time I publish.

I don't know anything about ASP. Dealing with this web site is only about 5%
of my job, and athough it would be cool to learn a bunch of new stuff, I
simply don't have the time to rewrite the entire site. I was hoping it was
simply some setting or something stupid I'd done.

Thanks!

 

[Stefan B Rusynko]

Does that folder / subweb really have a space in its name as in "Staff Area"
- that will cause you problems in FP and on your server
If so, Convert it back to a folder, and rename it to remove the spaces as say "Staff_Area"

On some hosted servers you can not publish subwebs directly and must publish the root including subwebs
(after creating empty subwebs by the same names on the host server)

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Making each staff members folder a subweb didn't work. It made things
| worse when I tried to publish and eventually locked up my computer.
|
| This problem started then I made the "Staff Area" a subweb of our company
| web site. It was necessary to do this because I wanted a completely different
| set of shared borders, theme, etc. for the staff area (and I didn't want to
| have to make all the buttons/menus/drop downs manually - way too many pages
| and my boss is constantly having me change things around).
|
| I never had any trouble publishing to the password protected "staff area"
| directory before when the web site was just ONE site. When I changed the
| "staff area" folder to a subweb, that is when the problems started. Then,
| when my boss needed me to add a custom personal page for each staff member,
| without anyone else being able to see it, my problems multiplied. This is why
| I'm currently removing and then replacing the passwords on the folders each
| time I publish.
|
| I don't know anything about ASP. Dealing with this web site is only about 5%
| of my job, and athough it would be cool to learn a bunch of new stuff, I
| simply don't have the time to rewrite the entire site. I was hoping it was
| simply some setting or something stupid I'd done.
|
| Thanks!
|
| "Mike" wrote:
|
| > Community Message Not Available

 

[Mike]

Jennie

You stated the following:

<" I'm currently removing and then replacing the passwords on the folders
each
time I publish. ">

How are you replacing the passwords each time?
What program are you using to add a password to a folder?

Mike..

 

[Jennie]

The passwords for the Staff Area and the Personal web pages folders is all
done from the domain end. The control panel that LunarPages (our SP) uses is
called CPanel. It's version X (10). So, I go to CPanel and select "Password
Protected Directories" to set the Password Protected Resourse names, user
login ID's and user passwords. I don't have to redo the user names and
passwords - those remain. It's the protected resource names that have to be
recreated in order for me to publish the entire web, with the two subwebs.

Removing the "lock" on the 55 or so directories is simple. I just uninstall
FrontPage extensions (which automatically removes the protected resource
names, essentially unlocking all the folders). Then I reinstall the FrontPage
Extensions, publish my web site (including subwebs), then go to "Password
Protected Directories" in CPanel and give each folder a Protected Resource
Name again and save the changes for each folder. It's the navigation to each
folder in CPanel that takes forever.

I will change the name of the main folder "Staff Area" to "StaffArea" as
suggested. No other folder name has a space in it, so I'm not sure if this
will help or not, but it can't hurt to try!

Thanks for your suggestions. I appreciate it.

 

[Mike]

Hey Jennie,

Normally in Frontpage, open the site up from the server, then you would go
to the Menu and Select - Tools
Then - Server
Then - Permission or Administration Home
Your browser will launch to the server administation area for your site.
Enter you user and password

and this is where you add users with their Permission Rights. You can even
set it up for them just to Browse and View Pages Only and even if they have
access to Frontpage, they could not make any changes.

For it to asked them for their password, you will have to set "Anonymous
access = off". This will prompt ALL visitors for a password.

From this area, you can change the settings for "Anonymous access = off",
then it will prompt them for a password to access this subweb.

I have found it easier to convert the folder to a subweb from Frontpage and
then go into this area and set the permissions from here. From the admin
area, you can Create A Subweb, but in Frontpage, you can Convert A Folder to
a subweb.

Also when you create a subweb, are you creating it from Frontpage or from
your Cpanel?

Hope this helps,
Mike...

 

[Thomas A. Rowe]

The problem is that you are setting the password outside of FP/FPSE, so FP has no way of working
with them.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

 

[Jennie]

Well, duh!!! hahahahaha

I knew it was something really stupid I'd done. I picked up this web site
after it had already been developed with passwords set through the service
provider, so I assumed it had been setup correctly. I should have done more
research.

I'll get right on changing all of it over to the FrontPage Server
Administration.

Boy, do I feel dumb! Thanks for everyone's assistance. I really do
appreciate it!

 

[Stafs]

Hi
On a similar vein I wondered if anyone could help me. I run a website that
has a secure area that people subscribe to.

The security is set up as Mike described - as a sub web and giving users a
name and password and browsing permissions.

The problem I have is that I want to be able to do one of two things -
either restrict each sign on so that it can only access the site once to
prevent people from sharing their user ID's (so no simulatenous use of the
same user name from 2 seperate IP addresses),

OR preferably be able to report on the use of the users ID's - IE log
in/out time and IP address.

I have asked my web host if they can report the sign on information for me
and they insist that they cant. Is there a way I can build in a log into the
site?

Thanks in advance for your help..................Glen

 

[Stefan B Rusynko]

Depends on your server OS and what they support
Would require use of server side scripting (custom coded to log user in and flag a use is currently logged in) and a database
- even then it is not reliable unless they also actually log out

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Hi
| On a similar vein I wondered if anyone could help me. I run a website that
| has a secure area that people subscribe to.
|
| The security is set up as Mike described - as a sub web and giving users a
| name and password and browsing permissions.
|
| The problem I have is that I want to be able to do one of two things -
| either restrict each sign on so that it can only access the site once to
| prevent people from sharing their user ID's (so no simulatenous use of the
| same user name from 2 seperate IP addresses),
|
| OR preferably be able to report on the use of the users ID's - IE log
| in/out time and IP address.
|
| I have asked my web host if they can report the sign on information for me
| and they insist that they cant. Is there a way I can build in a log into the
| site?
|
| Thanks in advance for your help..................Glen
|
|
|
|