The moss site also supports configuration methods for Windows integration verification and form verification (4)

In the previous article, we configured form verification for the mirror site, that is, we found that the user has no management permissions after login. Next we will reset the permissions for it.

1. First, open the Home Directory of the management center site and modify its web. config file. In the previous article, modify <connectionstrings> and <membership> in the same way as the image site.

2. Go to the Management Center page and click "Web application policy" on the "Application Management" page ".

3. On the "Web application policy" Management page, click "Add User.

4. On the "Add User" Page, select our site and region and click "Next.

5. Click "Browse user" in the "Select User" section.

6. the user browsing dialog box is displayed. In the search text box, enter your management account name, for example, "wssadmin", and click "Search" (a magnifier icon ), the following list lists the account information. You can find that the "account name" has the prefix "aspnetactivedirectorymembershipprovider. Click "add" at a single point and then click "OK.

7. when the dialog box is closed, you will find that the selected account already exists in the "Select User" text box, in the "select permission" section below, select the "full control" option and click the "finish" button.

8. Now, on the "Web application policy" page, we can see that we have added a fully controlled management account for the Intranet region. At the same time, we can see that the account is provided by our provider through the account name prefix.

Finally, log on to our image site using this account and you will find that he has full control permissions. This user can also add permissions to other users on the site.

In addition to "aspnetactivedirectorymembershipprovider", you can also use "ldapmembershipprovider ". For example:

In this way, different providers can be used for verification in different regions.

Of course, if you do not want to use ad for user management, you can also configure "aspnetsqlmembershipprovider" to use the database for user management. There are many introductions about its configuration on the Internet, so I will not describe it here. Of course, you can also write a provider by yourself.