How To Enable Active Directory for the Retail Solution Site

This step-by-step article describes how to enable Active Directory for the Retail solution site.

Active Directory is the Microsoft Windows 2000 directory service. With Active Directory, you can add, modify, delete, and organize the business entities of your organization. Commerce Server Profiles Resource manages the collection of data on your Web site. This collection of data is stored in data sources that control where the data is stored when it is collected.

You can use Active Directory as a data source for profile data. The Profiling System aggregates data from Active Directory and from other data sources into a single business entity that you can then use in your Commerce Server implementation.

The example that is in the following section provides a scenario in which to create a user profile definition that stores data in both a Microsoft SQL Server database and in an Active Directory database; in this example, the Retail and Supplier Active Directory solution sites are used.

How to Enable Active Directory, AuthFilter and Windows Authentication for the Retail Solution Site

The following example is provided only to describe the process; it does not describe an actual profile that you should use. You need to design your profile definitions based on your business requirements.

The following example is based on the assumption that you have installed and configured Active Directory domain controllers for your Commerce Server 2000 site.

NOTE: If you do not have the domain controller installed on the same computer as Commerce Server, refer to the "Troubleshooting" section in this article.

Create a User Profile Definition That Stores Data in a SQL Server Database and in an Active Directory Database

NOTE: In the online product documentation go to the section entitled "Enabling AuthFilter for the Supplier Solution Site", which is located in the following location: You need to refer to this documentation to complete some of the following steps.

1. Use the Commerce Server Site Packager deployment tool to perform a custom unpack of the Retail solution site. While you are using the tool, use the default configurations except on Select Resources, where you need to remove the Profiles Resource.
2. Use Commerce Server Site Packager to perform a custom unpack of the Supplier Active Directory solution site. Use the default configurations of the deployment tool except in the following areas:
   • On the Unpack Method page, select Add resources in the package to an existing site.
   • On the Select Site page, select the Retail site unpack in the previous step.
   • On the Select Resources page, add only the Profiles resource from the list of available resources. You can also specify a new database name for the Profiles tables. If you do not modify this, you receive the following warning message:
     Some databases you have specified already exist....want to continue?
     Click Confirm to continue.
   • On the Profiling System page, type the domain name, the user name, the password, and the parent URL. You can use the default for the parent URL, or you can modify it according to the Organization Unit (or Units) that you need.
   • On the Profiling System page, type the following:
     
     
     • domain name
     • user name
     • password
     • parent URL
     NOTE: You can use the default for the parent URL, or you can modify it based on the Organization Units (OUs) that you need.
3. In Computer Management, click Commerce Server Manager, click Commerce Sites, click Applications, right-click the Retail application, and then click Properties.
4. On the General tab, in the Authentication filter box, select Windows Authentication, and then click OK.
5. In Computer Management, Click click Internet Information Services, right-click the Retail site directory, and then click Properties.
6. On the Directory Security tab, under the Anonymous access and authentication control section, click Edit.
7. In the Authentication Methods dialog box, enable only Basic authentication. Click Edit, and then specify the domain name in the Basic Authentication Domain dialog box.
8. In Computer Management, click Internet Information Services, right-click Retail site directory, and then click Properties.
9. On the Directory Security tab, under Anonymous access and authentication control, click Edit.
10. In the Authentication Methods dialog box, enable only Anonymous access on the directory.
    
    NOTE: If you are using a Web farm, or if you require a proxy account support, please refer to the "Troubleshooting" section in this article.
11. Go to the "Enabling AuthFilter for the Supplier Solution Site" section that is mentioned in the note prior to step 1. In the "Enabling AuthFilter for the Supplier Solution Site" section:
    • Step 10 has the required code that you need to update the GetUserInfo method in the Std_access_lib.asp page, which is located in the \Retail\Include folder.
    • Step 11 has the required code that you need to update the PrepareLoginSection method in the Menu.asp page, which is located in the \Retail\Template folder.
12. Use Business Desk to create a new user for the Retail site.
13. Go to the URL, http://computername/Retail, and then type the credentials on the Login.asp page.
14. To allow users to register themselves, you need to create your own registration page.

TROUBLESHOOTING

• If Commerce Server is installed on a separate computer than the domain controller, you must trust the Commerce Server for delegation.For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
  298549� Enabling AuthFilter for the Supplier Solution Site Missing Steps
• If you are using a Web farm, or if you require a proxy account support, please refer to the product documentation "Login.asp code for the Supplier Solution Site" in the following location:
  Commerce Server 2000\Administering Commerce Server\Login.asp code for the Supplier Solution Site
  You will also need to test this section thoroughly because this has not been tested for this article.

For additional information, click the article numbers below to view the articles in the Microsoft Knowledge Base: