Home Links Imagemap services application how to
FAQ
 

 

WebDAV Administrative Interface
Frequently Asked Questions

  1. How do I access the admin interface?
  2. How do administrators manage access privileges?
  3. Why are there already two groups defined?
  4. How do I create a group?
  5. How do I delete a group?
  6. How do I add users to a group?
  7. How do I remove users from a group?
  8. How do I assign directory permissions to a group?
  9. Why can't I change some permissions for the webadmin group?
  10. Why can't I change any permissions for the admin group?
  11. What if I don't know someone's Directory ID?
  12. What if I input the wrong Directory ID?
  13. What if users don't know their Directory ID and password?

1. How do I access the admin interface?
In a web browser go to http://www.[yoursitename].umd.edu/cgi-bin/davadmin.pl. This will take you to a secure connection and prompt you for your University Directory ID and password. [Note: If your site is not part of the ".umd.edu" domain, replace that with ".org", or ".net" as applicable.]

2. How do administrators manage access privileges?
Access to website content and scripts for maintenance is managed on a per-directory basis. Site administrators create groups, grant or deny access to directories to groups, and assign users to groups. For a user to edit content in a particular directory, they must be a member of a group with priveleges on that directory. Site administrators will use the administrative tool to:

  • Control access to content by adding individual content managers to groups assigned with specific access privileges.
  • Determine which areas of the site will be publicly available. For information regarding controlled public access consult the htaccess Administration FAQ.

3. Why are there already two groups defined?
There are two default groups that exist for every site on the Webhosting server:

  • "webadmin" is a group that has privileges to edit all content of the site. This means that members of this group can edit all documents, create new documents, create new directories, etc.
  • "admin" is a group that has privileges throughout the entire site, including content, scripting, and user management. Members of this group can edit files in the cgi-bin directory, change the analog configuration file, clean out the old logs directory, all in addition to having full access to the content area outlined above. Members of the admin group can also access the administrative interface to create new groups, add members to existing groups, remove members from existing groups, and delete groups. Access to this group should necessarily be limited.

These groups are, as their names imply, administrative groups. Grant membership accordingly.

4. How do I create a group?
From the Access for Content Provders page simply enter the name of the new group in the text box provided and click on "Create a new group" button. If you try to create a group name with spaces or disallowed special characters, you will be told that the group name is not valid. If you enter a valid group name, the group will be created and you will be taken to a page that allows you to populate the new group and set directory permissions.

5. How do I delete a group?
From the Access for Content Provders page identify the group you wish to delete by slecting the box to the left of the group name and click the "Delete selected group(s)" button. When prompted to confirm, select "Delete" to delete the group.

6. How do I add users to a group?
From the Access for Content Provders page click on the group you would like to modify. Enter the Directory ID of the user you would like to add and click on the "Add user to group" button.

7. How do I remove users from a group?
From the Access for Content Provders page click on the group [the name of the group is a hyperlink] you would like to modify. Select the member to delete by clicking the box to the right of the user name. When prompted to confirm, click "Delete" to remove the user from the group.

8. How do I assign directory permissions to a group?
From the Access for Content Provders page select the group you would like to modify. Click the "modify access" link at the bottom of the page. Click "grant" to grant access to a particular directory. Click "deny" to deny access to a particular directory. Directories that a group has permission in appear as green in the colored status bar. Directories for which the group does not have permissions appear as red in the colored status bar.

9. Why can't I change some permissions for the webadmin group?
The webadmin group has permissions to edit all content of the site. This cannot be denied. If you have a member of the webadmin group who shouldn't have permissions in a particular directory, you must remove that member from the webadmin group and add them to groups with the proper permissions.

10. Why can't I change any permissions for the admin group?
The admin group must have privileges for all directories necessary to administer the site. Populate this group only with members who will be acting as co-administrators for the site.

11. What if I don't know someone's Directory ID?
Click on the "Discover User's Directory ID" link to the right of the text box on the "Add user to group" page. This will open a new browser window. Conduct a search for the user's name. If the user appears in the results list, copy the string that appears to the right of the user's full name. This string is the user's Directory ID. Close the pop-up window and paste the Directory ID into the "Add user to group" box. Press the "Add user to group" button.

12. What if I input the wrong Directory ID?
The intended user will not be able to access their pages. You will have to remove the incorrect ID and add the correct one.

13. What if users don't know their Directory ID and password?
Have the user visit http://directory.umd.edu and initiate the discovery process.

 

Links Imagemap sevices application how
University of Maryland Maintained by theOffice of Information Technology
Please direct comments to webhostingadmin@umd.edu
Last modified November 19, 2007

Office of Information Technology