SharePoint 2013 Configure forms-based authentication

Objective

Here's a quick introduction to configuring forms-based authentication for SharePoint 2013, simply by creating a database with the tools provided by NET, and then configuring the SharePoint Central Administration, the STS service, and the three Web. config for your application. Let's look at the process of creating it in a graphic way.

Using the tools provided by Microsoft, create a database and find the aspnet_regsql under Framework64, such as:

Here I found C:\Windows\Microsoft.NET\Framework64 v2.0.50727 path and v4.0.30319 path under the file, try to run separately, found no difference;

Double-click Aspnet_regsql, pop up the Create Wizard, click Next, such as:

Select the installation option that we are going to configure, not remove, such as:

Fill in the database server name and database name, I am here a separate instance, not the default instance, so the server looks strange, such as:

Confirm that your settings are not correct, such as:

Database has been created or modified, we can connect to the database to view, such as:

Open the SQL Server Administration tool and you can see the databases and tables that we created, which have indeed been created, such as:

And then modify the CA, STS service, web App's config can;

Open IIS, locate the central Administration site from IIS, right-click, and modify the configuration file, such as:

Of course, if you are very familiar with, go directly to find the configuration file can;

The following configuration file, open with Visual Studio, Notepad can also, but the structure is not clear;

Add a database connection string (between </SharePoint> and <system.web>) in the following location, such as:

<connectionstrings><add name="sqlconnectionstring " connectionstring= "  Data Source = db;initial Catalog = formauthenticationdb;integrated Security = SSPI"/></ Connectionstrings>

Add membership Provider and role Provider in the following locations

<membership defaultprovider="linyumembership"> <providers> <add name="linyumembership"connectionStringName="sqlConnectionString"passwordAttemptWindow="Ten"enablePasswordRetrieval="false"enablePasswordReset="true"requiresQuestionAndAnswer="false"ApplicationName="/"requiresUniqueEmail="true"Passwordformat="Hashed"type="System.Web.Security.SqlMembershipProvider, system.web, version=2.0.0.0, Culture=neutral, publickeytoken= B03F5F7F11D50A3A"/> </providers></membership><rolemanager defaultprovider="Linyurole"> <providers> <add name="Linyurole"connectionStringName="sqlConnectionString"ApplicationName="/"type="System.Web.Security.SqlRoleProvider, system.web, version=2.0.0.0, Culture=neutral, publickeytoken= B03F5F7F11D50A3A"/> </providers></roleManager>

Complete, overwriting empty nodes that already exist, such as:

Modify the configuration file for the STS service to be found through IIS, such as:

Add a database connection string below </system.serviceModel>, such as:

Add the <system.web> nodes and membership Provider and role Provider directly below, such as:

Modify the Web app's configuration file, such as:

Under </SharePoint>, add a database connection string, such as:

Locate the location and add our nodes, such as:

Add complete, such as:

To this, the configuration files are modified successfully, to the central administration to modify the Web App certification.

Open Central Administration, locate the Web application that we want to configure, and click Verify provider, such as:

Tick the FBA certification and fill out our membership and provider, then save, such as:

Open the site, you can already choose the way to login, such as:

Select the form to log in and go to the landing page (but you cannot log in at this time because there is no user to add form authentication for the site), such as:

Go to the Admin Center, modify the site collection administrator, and look for users who have been added, such as:

Then use Linyu to log in, you can find that has landed, indicating that the form authentication configuration success!

To view user information, the account name is indeed a form-certified account, such as:

Summary

In fact, the configuration of form authentication is a basic configuration of SharePoint development, take out is also a reference for everyone, hoping to bring help to the people in need.

SharePoint 2013 Configure forms-based authentication