Forms Authentication in MOSS 2007: IFs and WHYs
Part 1 of 4. Database Creation
Since the beta days of MOSS 2007, we are bombarded by articles and blogs on forms authentication. I’ve enjoyed an ample benefit form those writings when I’ve implemented this model into operation few quarters ago. It was successfully employed! However, not to censure the gift of copy-paste, I ended up without understanding the IFs and WHYs of the process. The reason why I have revisited this item! In addition, I am writing this piece for those who are recently evangelized on the bizarre features of Microsoft Office SharePoint Server 2007.
Forms authentication could be implemented in four segments, where the first three are only preparatory strides. Moreover, we will devide this paper into four parts since it could not be accommodated in a single publication.
1. Database Creation
2. User Creation
3. Portal Creation
4. Forms Authentication
1. We will start by exploring C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 and execute aspnet_regsql.exe. As shown below, we will be prompted by an ASP .NET SQL Server Setup Wizard. Then, click Next.
WHY ASP .NET SQL DATABASE? It is designed to store information for ASP .NET applications services, e.g. membership, role management, profile, et al. Without writing any line of SQL script, we are automatically provided of necessary tables, views, and stored procedures. And we the same stuff, we are immediately empowered to utilize all the features of ASP .NET Web Site Administration Tool and Login controls – e.g. Login, Login View, Password Recovery, Login Status, Login Name, User Creation Wizard, and Change Password.
2. Upon clicking the Next button of the Welcome window of the wizard, we will be prompted by a window where we are going to select the setup option. Since we are going to create a new database, we need to select the Configure SQL Server for Application Services option, then click Next. Below is the illustration.
3. Below is the next window of the wizard where we are going to define the server and database we will be using. For the purpose of this piece, we will be naming our database as PointMembership. Then, click Next and Finish to finalize the our first preparatory step.
IF <default> DATABASE IS USED? No predicament! Only that the initial catalog of our connection string in the proceeding item must be pointed to aspnetdb.
End of Part 1 of 4