This section describes basic tasks associated with setting up native access control. Native access control provides authenticated access for both Java-based and non-Java applications. However, if you plan to deploy Java web applications, you can leverage the benefits of Java-based security realms. The various aspects of Java security constraints are outside the scope of this guide but are discussed in detail in the Sun Java System Web Server 6.1 Programmer’s Guide to Web Applications.
For more information on the various aspects of Java security, see Sun Java System Web Server 6.1 SP10 Programmer’s Guide to Web Applications.
Here is a simple exercise that illustrate how a native ACL is configured. To use a combination of host-based and user-based access control perform the following tasks:
Consider that you want to allow access to all files under /hr/publish/manager to a user named “manager” at Acme Corp. To use user-based access control (in addition to host-based access control), create a directory service
Since you use you first need to .
Set up user information in a file
Obtain user information from an LDAP server
In this example, we will set up user information in a file.
Access the Administration Server and choose the Global Settings tab.
Click the Configure Directory Service link.
From the Create New Service of Type drop-down list, choose Key File as the type of directory service. This is a text file that contains the user’s password and the list of groups to which the user belongs.
Specify keyfile1 as the Directory Service ID and HRAuthFile as the name of the file, as shown below:
Click Save Changes.
Restart the server for the changes to take effect.
We start with creating a user ID called “manager.” This will represent the person who needs to have access to all the files in /hr/publish/manager .
Access the Administration Server and choose the Users & Groups tab.
Click New User.
Select “HRAuthFile” from the Select Directory service drop-down list and click Select.
Enter the required information, as shown below:
Click Create User.
A new user is added to the file: HRAuthFile.
Next, you need to associate our virtual server, hr.acme.com, with the directory service we’ve created.
Access the Virtual Server Manager and click the Settings link to display the Settings page for the virtual server, hr.acme.com.
Click the Edit link next to the Directory Services setting.
Select keyfile1 in the Pick Directory Services for Virtual Server page as shown below:
Click OK and then Apply to save and apply your changes.
Now you can specify the required access control rules.
Start by creating an ACL for the virtual server hr.acme.com .
Access the Server Manager and choose the Preferences tab.
Click the Restrict Access link.
Under the Option column, select the ACL file. We choose the default file in our example and click OK.
Select Pick a Resource and then specify the following wildcard pattern to control access to all files in the /hr/publish/manager directory :
Click the Edit Access Control button.
Check the “Access control is on” checkbox and click the New Line button.
Click on Deny in the second row of the Action column.
This opens the Allow /Deny page in the lower frame of Figure 3-8: Restricting Access Control
Click Allow, if not selected by default, and then click Update.
Click on “anyone” in the Users/Groups column, in the top frame.
Enter “manager” as the user you will allow access to, and keyfile1 as the authentication database, in the User/Group page that appears in the lower frame of Figure 3-9: Access Control for User and User Groups
Click Submit to store the new access control rules in the ACL file.
Click Apply Changes and save and apply the changes that you have made.
Once an ACL is set users accessing the site will be required to authenticate themselves before they are allowed access, as shown below: