Elczar Adame's Shared Points on SharePoint


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

 

 

 

 

 

Advertisements

Comments on: "Forms Authentication in MOSS 2007: IFs and WHYs – Part 1 of 4" (8)

  1. thanks, i knew sharepoint supports forms authentication, been looking around and this article is the first and the most straightforward that i got. Thanks sir luke!

  2. Thanks John…

  3. is it posible to use both Forms and AD auth on same site? one scenario would  be, corporate users will logon using their intranet / Active directory account, while customers will have to sign-in using forms.

  4. Hi John,
     
    This is possible by extending your internet site (forms authentication) to an intranet site (Windows authentication). Both have the same source but hosted in different ports.
     
    You can set it through Central Administration > Operations > Global Configuration > Alternate Access Mappings. For details, please visit http://technet.microsoft.com/en-us/library/cc263208(TechNet.10).aspx.
     
    Thanks.

  5. carmela.manansala said:

    Hi Elczar,
     
    I just followed your post: Forms Authentication in MOSS 2007: IFs and WHYs 1-4. Unfortunately im having a problem in part 4 number 11, When i changed the Primary Site Collection Administrator by the user i have created in the database and click the check user or address book icon, i can\’t see the user i have created and come up with an error "no exact match was found", also when i try to logon it seems that my extended web app did not accepted the forms user i have created in VS2005 tool. What do you think is the problem? thanks!.
     

  6. Hi Carmela,
    Thanks for referencing my post. By the way, please check the changes that should be made in the Web.config file of your Central Administration and Web application. Then make sure that the user is properly provision. It should capture the user as Provider Name: User Name (compared to Windows authentication that captures the user as Domain Name\\User Name).
     
    Please let me know if this helps you solving the problem. Thanks.

  7. carmela.manansala said:

    Hi Elczar,
     

    thanks for helping! it works!.

  8. Thanks Carmela for the feedback.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Tag Cloud

%d bloggers like this: