• Article

Configure SQL Server-based forms authentication in Project Server 2010

 

Applies to: Project Server 2010

Topic Last Modified: 2009-10-28

This article describes how to configure Microsoft Project Server 2010 forms-based authentication using SQL-based forms authentication. This procedure uses Claims authentication and SQL Server on the domain in which your Microsoft Project Server 2010 deployment is installed.

In order to perform these procedures, you must be member of the Project Server, Microsoft SQL Server, and Microsoft SharePoint Server administrator groups on the local computer.

Configure SQL Server-based forms authentication in Project Server 2010

To create the SQL authentication store

  1. Log on to any Windows Server on the farm running ASP.NET as a user with the DBCreate and SecurityAdmin permissions for the computer running SQL Server that will be used.

  2. At a command prompt, run %WINDIR%\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe -S <InsertSQLServerName> -d <InsertDBName> -E –A mr to create the authentication store database on the computer running SQL Server.

  3. Add all farm accounts to the DBO role for this newly created database.

To configure SharePoint Server for SQL authentication

  1. Create a new Web application in Claims mode.

    Note

    A Web application that is already in Windows Classic mode cannot be used.

  2. Go to the SharePoint Central Administration Web site.

  3. Click Application Management.

  4. On the ribbon, click New. A pop-up window appears.

  5. In the pop-up window, select the Claims Based Authentication option.

  6. In the pop-up window, in the IIS Web Site section, select a unique name and port number.

  7. In the pop-up window, in the Security Configuration section, set Allow Anonymous = No and set User SSL to Yes or No, depending on whether the site you are extending will be SSL-enabled.

  8. In the pop-up window, in the Identity Providers section, check Enable Windows Authentication and select NTLM if Integrated Windows authentication will be used. Also select Enable ASP.NET Membership and Role Provider and specify a provider name and role manager.

  9. In the pop-up window, keep the default setting for Public URL.

    Note

    This setting can be changed later if necessary.

  10. In the pop-up window, in the Application Pool section, choose to create a new pool with a pool name and the account that will be used.

  11. In the pop-up window, after Database Name set the value for the SQL server and database names for the content database.

  12. Click OK to close the window. A new IIS Web site will be created.

  13. Once you have received confirmation that the IIS Web application is created, you must create a new site collection at the root: Click Application Management in Central Administration, click Create Site Collections, and in the Web Application drop-down list, select the newly created claims-mode Web application.

  14. In the URL section, enter the root "/".

  15. Select the Blank Site template and specify a Windows user account in the Site Admin box.

  16. Click OK.

To configure the SQL authentication provider

  1. Edit the connection strings to the SQL Server database membership store. This data is provided in the .config files that are used by the application at every request.

    Note

    The three Web configuration files to modify to connect to the AD-LDAP membership store are the .config files for the following: Central Admin, Security Token Service, and the content Web Application.