Technical article 105707

Configure Netscape FastTrack user HTTP publishing with no Unix user account.

OpenServer 5.0.4

Written · Last revised

Problem

I want to configure the FastTrack server so that users can publish web content using HTTP (Hyper Text Transfer Protocol), and so that:

1) users have no Unix shell, 2) users have access only to their own directories, and 3) user access is authenticated by the HTTP server.

With this configuration, users cannot publish using ftp.

Solution

The FastTrack server has its own user database, and is able to authenticate users who are using HTTP web publishing, even if they have no Unix account. Cases in which a Unix user account is required are not considered in this article.

Using your Netscape browser, access the Netscape Server Selector at:

http://localhost:445
Enter authentication information, if prompted.

Click on the number denoting the server you want to configure. The number consists of the server's port and IP address, separated by a period. You will be presented with the FastTrack server management interface.

The management interface consists of three frames a top frame with the main menu bar (as well as Choose and Apply buttons), a frame on the left, with a column of menu items for the current management function selected in the main menu bar, and a third frame with forms for the current management function.

Click on the System Settings button on the main menu bar. Click on View Server Settings in the menu column. Under:

Content Settings (obj.conf)
 For the entire server:

note the Primary Document Directory, and any Additional Document Directory or Public Directories Mapping that may have been configured.

In the following example, we create a directory for our new user, "blorf", under the primary document directory:

/usr/internet/ns_httpd/docs

(In practice, the directory can be any one of the directories noted in the prior step.) The "#" indicates the Unix command line prompt:

# cd /usr/internet/ns_httpd/docs
# mkdir blorf
# chown nouser blorf
# chgrp nogroup blorf
# chmod 755 blorf

Create a similar directory for each new user.

Now return to the FastTrack Server Manager to configure the user in the server database, and to set publishing access control on the user's directory.

Click on the Access Control button in the top menu bar. With Create User highlighted in the Access Control menu, in the Login Name field enter the name the user will use when publishing. In the Full Name field, enter the real name of the person who will use the login name. Enter the user's password in the Password and Again fields.

Note: You may click on the Help button at the bottom of this and other pages to access online help about the current management function.

Click on the OK button, and on the subsequent confirmation button.

Click on Restrict Access in the Access Control menu. In the Editing: line, click on Browse to move to the Choose a Part of Your Server page.

If the Current Directory line shows the directory under which you made the new user directory, the new user directory will appear in the listing below; click on that item to return to the Restrict Access page, and confirm that the new user's directory is highlighted in the Editing picklist.

If, on the other hand, the Current Directory line doesn't show the directory under which you made the new user directory, click on Options, and in the List From field, enter the absolute path of the directory under which you made the new user directory. Click on OK to return to the Choose a Part of Your Server page, and click on the new user directory. As in the first case, this returns you to the Restrict Access page; confirm that the new user's directory is highlighted in the Editing picklist.

Click on the Turn On Access Control button. For Access Type "Read",
the Action is "Allow"; for Access Type "Write", the Action is
"Deny".  Click on the Permissions button for Access Type "Write".
With the Allow These Users and Groups radio button selected, enter
the new user's login name in the Users field, and click on the Done
button. When you are returned to the Restrict Access page, click on
the OK button, the Save and Apply button, and the subsequent
confirmation button.

Click on the Content Management button in the main menu bar. Click on Remote File Manipulation in the menu column. In this instance, check that the new user's directory, rather than the directory above it, is chosen on the Editing line; if necessary, use Browse and Options, as explained above. Select the Yes radio button under Activate File Manipulation Commands, click on the OK button, the Save and Apply button, and the subsequent confirmation button.

You can review the changes made by returning to the View Server Settings page.

Try editing and publishing a test page using Navigator Gold:

File -> New Document -> Blank
Type some unique phrase ... "blorf test 1"
File -> Save: /tmp/index.html
File -> Publish:

Publish: /tmp/index.html Upload Files to this location (FTP or HTTP): http://<servername>/blorf User name: blorf Password: <password>

File -> Open Location: http://<servername>/blorf

It is recommended that you click on the Help button for each page that provides one, and review that portion of the documentation to help you understand clearly the changes being made.

NOTE:     If you see rapidly repeating server startups in the error log, you
          may need to manually stop and start the server every time you
          "save and apply".

See also

Manual pages for mkdir(C), chown(C), chgrp(C), chmod(C).

From the Xinuos technical article database, record 105707. Reproduced with permission. The original is at www.sco.com/ta/105707, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.