Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How to Restrict End User Access on Netscape Enterprise Server


View products that this article applies to.

This article was previously published under Q216749

↑ Back to the top


Summary

In a standard configuration, it is not possible to restrict end-user access to FrontPage Webs on a Netscape Enterprise Server. This means that you would not normally be able to set the Only registered users have browse access option. With the FrontPage 2000 Server Extensions it is possible to make configuration changes that enable restricting end-user access. This article provides the steps necessary to do so.

↑ Back to the top


More information

To restrict end-user access on Netscape Enterprise by setting the Only registered users have browse access option, you will first need to load the shared library for .htaccess support. This information can be found in the online Help for your server and you should review it prior to proceeding. An excerpt from the online Help for the Netscape Enterprise Server that explains how to enable .htaccess is listed below:

If you have the FrontPage Server Extensions installed, you will need to uninstall them prior to making the configuration changes listed below.

If you have Dynamic Configuration activated, you will need to deactivate it prior to making the configuration changes below.

You should make a backup copy of the Obj.conf configuration file prior to editing it.

Using Htaccess Files

The files that support .htaccess are located in the server root in Plugins/htaccess. These files include a plug-in that enables you to use .htaccess files and a script for converting .nsconfig files to .htaccess.

When activating .htaccess, you must first modify the server's Obj.conf file to load, initialize, and activate the plug-in. At the top of the Obj.conf file, after the other Init directives, add the following lines:
Init fn="load-modules" funcs="htaccess-init,htaccess-find" \
shlib="server_root/plugins/htaccess/htaccess.so"
Init fn="htaccess-init"
These lines load and initialize the module when the server is started. Server_root is the path to your server root. The samples listed will likely be different than your server root. For instance, on Netscape Enterprise 3.0, it is shlib="/usr/local/www/netscape-enterprise/plugins/htaccess/htaccess.so." On Netscape Enterprise 3.5.1, it is shlib="/usr/local/www/netscape-enterprise/plugins/htaccess/bin/htaccess.so."

To activate .htaccess file processing for all directories managed by the server, add the following PathCheck directive:
PathCheck fn="htaccess-find"
to the default server object, which is delimited by:
<Object name="default">
...

</Object>
Generally, the directive to activate .htaccess processing should be the last PathCheck directive in the object.

After you edit the configuration file Obj.conf, stop and restart your server. Apply your configuration file changes in the Server Manager by clicking the Apply button. Subsequent accesses to the server will be subject to .htaccess access control in the specified directories.

The next step is to install the FrontPage 2000 Server Extensions. For additional information, see the following article or articles in the Microsoft Knowledge Base:
215481� Installing FrontPage Server Extensions to Netscape UNIX Server
After you install the FrontPage 2000 Server Extensions, your Web should be ready for use with FrontPage and should be configured for restricting end user access. If the server you are working with is Netscape Enterprise version 3.0 or earlier, you have completed all of the required steps. If your server is Netscape Enterprise 3.51, you will need to complete the remaining steps.

On Netscape Enterprise Server 3.51, it is necessary to modify a file in the _vti_pvt folder in the content area of the Web. The reason for this is that the Netscape Server does not read the Service.grp file correctly.
In the content area of your Web, locate the _vti_pvt folder and change the directory in it. Make a backup copy of the Service.grp file, and then edit the original Service.grp file by doing the following:

Remove the comment #FrontPage. and

Switch the order of Administrators and Authors. The file should look like the following:
authors:
administrators: admin
After editing and saving the Service.grp file, you should be able to open your Web and restrict end user access.

Because the Service.grp file was modified outside of FrontPage, you may not be able to use FrontPage to add new accounts with permissions to the Web, depending on your specific configuration. A possible workaround is to open the Web in FrontPage. At a UNIX command prompt, copy the backed-up Service.grp file to Service.grp. Chown the file to the UNIX User and Group of the Web, and use the FrontPage Client to add new accounts that you want. Again, it will be necessary to follow the steps above to remove the comment #FrontPage and swap the order of administrators and authors. Any time you need to add new accounts, you will have to use this workaround.

Note: Netscape does not officially support the use of .htaccess files to restrict access. As such, this is not a supported configuration. Please visit the Netscape Web site for more information:

↑ Back to the top


Keywords: KB216749, kbinfo

↑ Back to the top

Article Info
Article ID : 216749
Revision : 3
Created on : 2/22/2007
Published on : 2/22/2007
Exists online : False
Views : 327