Elczar Adame's Shared Points on SharePoint

Archive for September, 2007

Microsoft Office Outlook 2007 Integration


 

Microsoft Office Outlook 2007 Integration

I was once asked: “Is there an offline support for SharePoint lists and document libraries?” Yes there is! Using Microsoft Office Outlook 2007 as our offline client application.

Not to mention that this walkthrough is applicable as well for other SharePoint lists/libraries, we will be focusing on the integration and synchronization of SharePoint calendar with Outlook.

1.       In our Outlook My Calendar, we will create two activities. For our purpose, we will set them as:

a.       Outlook Activity A,  September 20, 2007, 9:00 AM to 10:00 AM.

b.      Outlook Activity B, September 20, 2007, 1:00 PM to 3:00 PM.

2.       In our SharePoint Calendar, we will create an activity. We will set  it SharePoint Activity A, September 20, 2007, 11:00 AM to 1:00 PM.

3.       Now we will start the integration. In our SharePoint Calendar page, click Actions, then Connect to Outlook. We will be transferred to Microsoft Office Outlook 2007 with the Connect this SharePoint Calendar to Outlook dialog box. Below is the illustration.

4.       In the same dialog box, let us click Advanced. We will be prompted by the SharePoint List Options dialog box. Below is the illustration.

5.       For our purpose, we will change the Folder Name to SharePoint Calendar, and leave the Update Limit being checked to update our subscription with the publisher’s recommendation. Then, click OK.

6.       In our Connect this SharePoint Calendar to Outlook dialog box, click Yes. Automatically, our SharePoint Calendar will be integrated in our Outlook under Other Calendars category. Below is the illustration.

7.       In our Outlook menu, let us click Tools, then Account Settings. The Account Settings dialog box will be displayed. Notice that our SharePoint Calendar is already listed in the SharePoint Lists. Below is the illustration.

8.        At rest in the Tools menu, let us point to Send/Receive, then to Send/Receive Settings, then click Define Send/Receive Groups. 

9.       In the dialog box as before, click Edit. The Send/Receive Settings – All Accounts dialog box will be displayed. Under our SharePoint account, as illustrated below, our SharePoint Calendar is included in our Send/Receive Options check list.

 

 

10.   To synchronize our SharePoint Calendar with the Calendar in our SharePoint site, let us click Tools menu, point to Send/Receive, then click Send/Receive All.

 

NOTE:  This is not a synchronization of SharePoint Calendar with Outlook My Calendar.

 

11.   To copy our Outlook My Calendar to SharePoint Calendar, let us select both Outlook Activity A and Outlook Activity B, the click Edit menu, then click Copy to Folder. The Copy Items dialog box will be displayed. Below is the illustrated results.

12.   In the Copy Items dialog box, under SharePoint Lists, select SharePoint Calendar, then click OK. Below is the illustrated results.

 

NOTE: The file is located in our C:\Documents and Settings\User Name\Local Settings\Application Data\Microsoft\Outlook directory as .pst file.

 

NOTE: If you roam Microsoft Office Outlook 2007, the SharePoint List is synchronized into a folder under the proxy .pst.

 

NOTE:  Any mismatched item will be detached and the original version  will be potted in the Local Failures folder.

 

 

13.   Lastly, let us click Tools menu, point to Send/Receive, then click Send/Receive All. Then, let us open our SharePoint site, and there we have a synchronized calendar items.

 

 

14.   Yet again, we can do the same Outlook integration with our SharePoint Contacts, Document Library, and Task List. Thanks.

Advertisements

SharePoint Web Part Template


 

SharePoint Web Part Template

With Windows SharePoint Services 3.0 Web Part using Microsoft Visual Studio 2005 Extensions, several steps we manually do when using Class Library or Web Control Library are automated – it simplifies the creation, deployment, and testing of Microsoft ASP.NET Web Parts in Windows SharePoint Services.

Web Parts in Microsoft Windows SharePoint Services offer us means to create user interface components that support both customization and personalization. The Windows SharePoint Services 3.0 Web Part infrastructure is designed and built on a layer over the Microsoft ASP.NET 2.0 Web Part infrastructure.

With an assumption that we have already installed and configured the Visual Studio 2005 Extensions for Windows SharePoint Services 3.0, we will create a calendar web part that could be displayed in the home page of our portal with link to our Calendar list.

Create Project

1.       Let us open our Microsoft Visual Studio 2005. In the File menu, point to New, then click Project.

2.       In the New Project dialog box, under Visual C# | SharePoint, let us select Web Part template. We will name our project WebPartTemplate. Then, click OK. Below is the illustration.

Initial Settings

1.       In our Solution Explorer, right-click Web Part project, then click Properties. The Properties window will be displayed.

2.       In the Properties window, as illustrated, we will select Debug. In the Start Action section, we will choose Start Browser with URL, pointing it to the SharePoint site where we will deploy our Web Part – e.g. http://Server Name:Port Number/.

3.       Still in the Properties window, we will select SharePoint Solutions to customize the Web Part solution feature package. The template automatically creates XML files necessary to package our Web Part as a Windows SharePoint Services 3.0 Feature. These are:

a.       Solution – written into the manifest.xml file for the Feature.

b.      Feature – written into the feature.xml for the Feature.

c.       Element – written into the element.xml for the Feature. It contains the information contained in a .webpart file.

Logic Description

using System;
using System.Runtime.InteropServices;
using System.Web.UI;
using System.Web.UI.WebControls.WebParts;
using System.Xml.Serialization;

using Microsoft.SharePoint;
using Microsoft.SharePoint.WebControls;
using Microsoft.SharePoint.WebPartPages;

using System.Web.UI.WebControls;

namespace WebPartTemplate
{
    [Guid("f72a2732-1bfc-4a95-8d24-b8c6e1302cae")]
    public class WebPartTemplate : System.Web.UI.WebControls.WebParts.WebPart
    {
        public enum PeriodEnum
        {
            Day,
            Week,
            Month
        };

        private const string DefaultList = "Calendar";
        private const PeriodEnum DefaultPeriod = PeriodEnum.Day;
        private const bool DefaultViewToday = true;
      
        private string List = DefaultList;
        private PeriodEnum Period = DefaultPeriod;
        private bool ViewToday = DefaultViewToday;

        Calendar calendar;

        public WebPartTemplate()
        {
            this.ExportMode = WebPartExportMode.All;
        }

        [Personalizable]
        [WebBrowsable]
        [FriendlyName("Calendar List")]
        public string CalendarList
        {
            get
            {
                return List;
            }
            set
            {
                List = value;
            }
        }

        [Personalizable]
        [WebBrowsable]
        [FriendlyName("Calendar Period")]
        public PeriodEnum CalendarPeriod
        {
            get
            {
                return Period;
            }
            set
            {
                Period = value;
            }
        }

        [Personalizable]
        [WebBrowsable]
        [FriendlyName("View Today")]
        public bool CalendarViewToday
        {
            get
            {
                return ViewToday;
            }
            set
            {
                ViewToday = value;
            }
        }

        protected override void CreateChildControls()
        {
            calendar = new Calendar();
            calendar.VisibleDate = System.DateTime.Today;
            calendar.SelectionChanged += new EventHandler(CalendarSelectionChanged);
            Controls.Add(calendar);
        }

        public void CalendarSelectionChanged(object sender, EventArgs e)
        {
            try
            {
                Page.Response.Redirect("~/Lists/" + List + "/calendar.aspx?CalendarPeriod=" + Period + "&CalendarDate=" + calendar.SelectedDate.ToShortDateString());
            }
            catch
            {
                Title = "Incorrect Settings";
            }
        }

        protected override void Render(HtmlTextWriter output)
        {
            output.Write("<table border=0 cellspacing=1 width=100%>");
            output.Write("<tr>");
            output.Write("<td>");
            calendar.RenderControl(output);
            output.Write("</td>");
            output.Write("</tr>");

            if (ViewToday)
            {
                output.Write("<tr>");
                output.Write("<td>");
                output.Write("Today is");
                output.Write("</td>");
                output.Write("</tr>");
                output.Write("<tr>");
                output.Write("<td>");
                output.Write(System.DateTime.Today.ToLongDateString());
                output.Write("</td>");
                output.Write("</tr>");
            }

            output.Write("</table>");
        }

    }
}

Notice the following items:

1.       We have added System.Web.UI.WebControl namespace directives for our calendar control.
2.       We have defined three objects/attributes:
a.       Calendar List – the name of our Calendar list in SharePoint where our calendar web part will be redirected.
b.      Calendar Period – the calendar period to be displayed during the redirection. The values are enumerated through PeriodEnum.
c.       View Today – an option to display the current date below our calendar web part.
3.       We have instantiated a calendar web control. Additionally, we can add reference to System.Drawing to set the skin our control.
4.       We have set an EventHandler, named CalendarSelectionChanged, for the SelectionChanged event of our calendar web control.
5.       Lastly, we have rendered our web part.

Deployment

As we have mentioned earlier, several steps that we manually do when using Class Library or Web Control Library are automated by the extensions. This is noticeable in the deployment process.
1.       Let us press F5. The extensions will automatically perform a number of tasks for us – e.g. assembly building, installing to global assembly cache, adding to SafeControls list, et al.  
2.       In our SharePoint page, click Site Actions, then click Edit Page.
 
For our purpose, our SharePoint page must have a Calendar list named Calendar, where our calendar web part will be redirected. Else, we need to set the Calendar List property of our Web Part later through Modify Shared Web Part by pointing it to a specific Calendar list.
3.       In a specific Web Part zone, click Add a Web Part to the Add Web Parts dialog box.
4.       Select our WebPartTemplate, then Add. Lastly, click Exit Edit Mode to have our final output.

I hope this would help!

 

 

Embedding InfoPath Form in SharePoint Page


 

Embedding InfoPath Form in SharePoint Page

Few weeks ago,  I was punctuated to embed an InfoPath form in SharePoint page. Immediately, I though of creating a custom web part or using SharePoint Designer. But hold on, InfoPath has already provided us this facility. By the good worth of “NO CODE” development model, it is the sensible solution:  XML Form View web part.

We initially need the following:

1.       A Form Library in SharePoint site. In this paper,  we will name our Form Library as Expense and our SharePoint site as Demonstration Portal.

2.       A browser-enabled InfoPath form published to our Expense Form Library. We will use the Sample-Expense Report and name it as Expense Report.

By the same token, we could use an administrator-approved form template, plainly uploaded and activated through Manage Form Template facility in the Application Management of our SharePoint 3.0 Central Administration. And we will get a hold of the same results.

1.       Upon completion of our two predetermined items, we going to add the following line in the <SafeControls> tag of the web.config file of our web application:

 

<SafeControl Assembly=”Microsoft.Office.InfoPath.Server, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” Namespace=”Microsoft.Office.InfoPath.Server.Controls” TypeName=”*” Safe=”True” />

 

NOTE: The web.config file of our web application is located at C:\Inetpub\wwwroot\wss\

VirtualDirectories\web application port number.

 

2.       Let us open our Demonstration Portal. Under Site Actions, click Site Settings.

3.       In the Site Settings page, as illustrated below, click Web Part Gallery link.

4.       In the Web Part Gallery page, click New. We will be redirected to the Web Part Gallery : New Web Parts facility.

5.       In the Web Part Gallery : New Web Parts part, check Microsoft.Office.InfoPath.Server.Controls.XmlFormView. Then,  click Populate Gallery. We will be redirected again to the Web Part Gallery page where we can verify the inclusion of XmlFormView.webpart. Below is the illustration.

6.       At this instant, we will employ the web part to put on view our Expense Report form. Let us open our Expense Form Library.

7.       In the Site Actions, click Edit Page. As illustrated below,  the page will be set to Edit Mode.

8.       Click the Add a Web Part link, and the Add Web Part to Main web page dialog will be displayed.

9.       Check the XmlFormView, normally under miscellaneous section, then click OK. If we will be prompted by an error message of InfoPath, we have nothing to worry. Just click Close.

10.   Now, we will modify our XmlFormView web part. To do this, click Edit, then Modify Shared Web Part.

11.   As illustrated below, let us set the following items,  then click OK.

a.       Editing Status : Editing

b.      Xsn Location : Please refer to the notations below.

NOTE:  The Xsn Location varies on the publishing approach we have employed.

a.       If we have published  our  form template directly to a specific Form Library, similar with our case, we can check the location from Site Actions, then Site Settings, then Site Libraries and Lists, then Customize Form Library, then click the corresponding Form Content Type, then Advance Settings, and we will have the URL of our form template. It is http://Server Name:Port Number/Form Library Name/forms/template.xsn.

b.      If we have published, however, an administrator-approved form template through the Manage Form Template facility, we can check the location from Site Actions, then Site Settings, then Site Content Types, then the corresponding Form Template Name – it is normally under the Microsoft Office InfoPath section, then Advanced Settings, and we will have the URL of our form template. It is http://Server Name:Port Number/FormServerTemplates/Form Name.xsn.

12.   As a final task, we will close the Expense list view, then Exit Edit Mode to have the final output.

I hope it will help you!

 
 
 
 
 

Forms Authentication in MOSS 2007: IFs and WHYs – Part 4 of 4


Forms Authentication in MOSS 2007: IFs and WHYs

Part 4 of 4 : Forms Authentication


After the three preparatory steps we have made – database, user, and portal creation – we are now ready to implement forms authentication.

1. We will start by writing additional lines in the web.config file of our Demonstration Portal and SharePoint 3.0 Central Administration.

2. To add some lines in the web.config file of our Demonstration Portal, open C:\Inetpub\wwwroot\wss\VirtualDirectories\5050\web.config.

3. Write the following lines before the <system.web> node:

<connectionStrings>

<remove name=”PointMembership” />

<add name=”PointMembership” connectionString=”data source=Server Name;Integrated Security=SSPI;Initial Catalog=PointMembership” />

</connectionStrings >

NOTE: Notice that the Initial Catalog is the database we have created.

4. Add the following lines inside the <system.web> node of the same web.config file:

<membership defaultProvider=”PublishingMembershipProvider”>

<providers>

<remove name=”PublishingMembershipProvider” />

<add name=”PublishingMembershipProvider”

type=”System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”

connectionStringName=”PointMembership”

applicationName=”/”

passwordAttemptWindow=”10″

enablePasswordRetrieval=”false”

enablePasswordReset=”true”

requiresQuestionAndAnswer=”true”

requiresUniqueEmail=”false”

passwordFormat=”Hashed”

maxInvalidPasswordAttempts=”5″/>

</providers>

</membership>

<roleManager enabled=”true” defaultProvider=”PublishingRoleProvider”>

<providers>

<remove name=”PublishingRoleProvider” />

<add name=”PublishingRoleProvider”

type=”System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”

connectionStringName=”PointMembership”

applicationName=”/” />

</providers>

</roleManager>

 

5. Now its time for us to add some lines in the web.config file of our SharePoint 3.0 Central Administration. Let us try to open our Internet Information Services, then right-click SharePoint Central Administration v3, then click Properties. In Home Directory tab, we could now have the path of our SharePoint 3.0 Central Administration.

6. Open the web.config file of our SharePoint 3.0 Central Administration and write the following lines before the <system.web> node:

<connectionStrings>

<remove name=”PointMembership” />

<add name=”PointMembership” connectionString=”data source=Server Name;Integrated Security=SSPI;Initial Catalog=PointMembership” />

</connectionStrings >

7. Add the following lines inside the <system.web> node of the same web.config file:

<membership defaultProvider=”PublishingMembershipProvider”>

<providers>

<remove name=”PublishingMembershipProvider” />

<add name=”PublishingMembershipProvider”

type=”System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”

connectionStringName=”PointMembership”

applicationName=”/”

passwordAttemptWindow=”10″

enablePasswordRetrieval=”false”

enablePasswordReset=”true”

requiresQuestionAndAnswer=”true”

requiresUniqueEmail=”false”

passwordFormat=”Hashed”

maxInvalidPasswordAttempts=”5″/>

</providers>

</membership>

<roleManager enabled=”true” defaultProvider=” AspNetWindowsTokenRoleProvider”>

<providers>

<remove name=”PublishingRoleProvider” />

<add name=”PublishingRoleProvider”

type=”System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”

connectionStringName=”PointMembership”

applicationName=”/” />

</providers>

</roleManager>

Notice that the defaultProvider is AspNetWindowsTokenRoleProvider.

WHY AspNetWindowsTokenRoleProvider? It is necessary because our SharePoint 3.0 Central Administration still uses Windows Authentication for the role provider.

8. Now we are going to set the Authentication Provider of our web application. Under the Application Security of our Application Management, click Authentication Providers link. Below is the figure.

 

9. In our Authentication Providers page, set our Web Application to http://servername:5050, then click the Default link. It will redirect us to Edit Authentication page. Below in the Authentication Providers page illustration.

10. In the Edit Authentication page, set the following items, the click Save. Below is the illustration.

a. Web Application – http://servername:5050

b. Zone – Default

c. Authentication Type – Forms

d. Anonymous Access – Enabled

e. Membership Provider Name – PublishingMembershipProvider

f. Role Manager Name – PublishingRoleProvider

g. Client Integration – No

 

11. Lastly, we will change the Primary Site Collection Administrator for our web application which we have created in the previous steps by the user we have created in PointMembership database. Below is the illustration.

 

12. Now we going to do some finishing steps. Let us browse our site at http://servername:5050. We will be prompted by the Sign In page. Log as user we created through ASP .NET Web Site Administration Tool and set as a Primary Site Collection Administrator.

WHY REQUIRED TO SIGN IN? WE HAVE ALREADY ENABLED THE ANONYMOUS ACCESS SETTING? What we have enabled in our previous item is the Internet Information Services anonymous access, or Web Application anonymous access in the field of SharePoint. We have not yet enabled the anonymous access for our site.

13. In the home page of our Demonstration Portal, click Enable Anonymous Access link. We will be redirected to Change Anonymous Access Settings page.

14. In the Change Anonymous Access Settings page, select Entire Web Site, then click OK. Below is the illustration.

 

 

Until now we are still logged as the Primary Site Collection Administrator. Point to Welcome Username link at the upper-right portion of our page, this click Sign Out. And we have already implemented forms authentication in our Demonstration Portal! We could now start implementing some enhancements  – might be in my next post. Hope it helps.

 

Forms Authentication in MOSS 2007: IFs and WHYs – Part 3 of 4


 

Forms Authentication in MOSS 2007: IFs and WHYs

Part 3 of 4 : Portal Creation


 

This part centers on portal creation as the last preparatory step in implementing forms authentication in Microsoft Office SharePoint Server 2007.

1. To start, let us open our SharePoint 3.0 Central Administration. In the Application Management tab, under SharePoint Web Application Management, click  Create or Extend Web Application, then Create a New Web Application. Below is the illustration.

 

 

2. In the Create New Web Application page, complete the following items, then click OK.

a. IIS Web Site

i. Select Create a New IIS Web Site

ii. Description – SharePoint-5050

iii. Port – 5050

iv. Host Header – Leave Blank

v. Path – C:\Inetpub\wwwroot\wss\VirtualDirectories\5050

b. Security Configuration

i. Authentication Provider – NTLM

ii. Allow Anonymous – No

iii. Use Secure Sockets Layer – No

c. Load Balance URK

i. URL – http://servername:5050

ii. Zone-Default

d. Application Pool

i. Select Create New Application Pool

ii. Application Pool Name – SharePoint-5050

iii. Select Configurable

iv. User Name – administratoraccount

v. Password – password

e. Reset Internet Information Services

i. Select Restart IIS Manually

f. Database Name and Authentication

i. Database Server – servername

ii. Database Name – PointContent-5050

iii. Select Windows Authentication

3. Upon creation of our new web application, as figured below, we will be prompted by an Application Created page. As instructed on the page, let us run first “iisreset /noforce” to finish the creation of our new IIS web site before firing the Create Site Collection link.

 

WHY “iisreset /noforce”? To avoid forcing the internet services to stop if stopping it precisely fails.

4. Click Create Site Collection link to create our Demonstration Portal. Below are the settings:

a. Web Application – http://servername:5050

b. Title and Description

i. Title – Demonstration Portal

ii. Description – For demonstration purposes only.

c. Web Site Address – http://servername:5050/

d. Template Selection – Publishing Portal

e. Primary Site Collection Administrator – administratoraccount

f. Quota Temple – No Quota

<

If you accidentally closed the Application Created page before site creation, we could access the Create Site Collection link from the Application Management page.

 

5. Finally, let us browse http://servername:5050 to check our newly created portal. Below is the illustration.

 

 


End of Part 3 of 4

Forms Authentication in MOSS 2007: IFs and WHYs – Part 2 of 4


Forms Authentication in MOSS 2007: IFs and WHYs

Part 2 of 4: User Creation


As we have mentioned in Part 1, this paper is divided into four parts, where the second part focuses on user creation necessary for the database we have created in Part 1.

1. To start, open your Microsoft Visual Studio 2005 and create a new web site.

WHY WE CREATE A USER? Upon setting the authentication type of our portal from Windows to Form, our Primary Site Administrator, which is a Windows or an Active Directory Account, will no longer be recognized. Thus, we need this user in our proceeding items to replace our Primary Site Administrator.

2. Write the following lines before the <system.web> node of the web.config of our newly created web site:

<connectionStrings>

<remove name=”PointMembership” />

<add name=”PointMembership” connectionString=”data source=Server Name;Integrated Security=SSPI;Initial Catalog=PointMembership” />

</connectionStrings >

NOTE: Notice that the Initial Catalog is the database we have created.

3. Add the following lines inside the <system.web> node of the same web.config file:

<membership defaultProvider=”PublishingMembershipProvider”>

<providers>

<remove name=”PublishingMembershipProvider” />

<add name=”PublishingMembershipProvider”

type=”System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”

connectionStringName=”PointMembership”

applicationName=”/”

passwordAttemptWindow=”10″

enablePasswordRetrieval=”false”

enablePasswordReset=”true”

requiresQuestionAndAnswer=”true”

requiresUniqueEmail=”false”

passwordFormat=”Hashed”

maxInvalidPasswordAttempts=”5″/>

</providers>

</membership>

<roleManager enabled=”true” defaultProvider=”PublishingRoleProvider”>

<providers>

<remove name=”PublishingRoleProvider” />

<add name=”PublishingRoleProvider”

type=”System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a”

connectionStringName=”PointMembership”

applicationName=”/” />

</providers>

</roleManager>

IF OTHER MEMBERSHIP AND ROLE PROVIDER NAMES ARE USED? No setback! Only that we have to synchronize other settings in the proceeding steps with the names we have assigned for membership and role providers.

IF NO MEMBERSHIP AND ROLE MANAGER ARE CONFIGURED? Still no setback! By default, a database is created in the App_Data folder of our web site to store membership and roles information. Hence, even without configuring our membership and role settings, the default providers will automatically be captured: AspNetSqlMembershipProvider and AspNetSqlRoleProvider. But in this case, we need to synchronize other settings in the proceeding steps.

4. Save the additions we have made in the web.config file.

5. It time for us to use the ASP .NET Web Site Administration Tool to create a user. In the Website menu of our Visual Studio, click ASP .NET Configuration. Below is the illustration.

6. Upon clicking the ASP .NET Configuration, we will be prompted by the Home page of ASP .NET Web Site Administration Tool.

WHY USING ASP .NET WEB SITE ADMINISTRATION TOOL? Basically, this tool is designed to facilitate changes in the site configuration without having to manually edit the Web.config file, in this case the configuration file of the site we have created and not the portal we will be creating. In our case, however, we use it to create a user and role for the corresponding membership and role providers which we  will be using later in our portal. Even the web site we have created in the previous steps has nothing to do with our portal. It is simple our way to access this tool.

NOTE:  The “How do I use this tool?” link would give us a comprehensive understanding of ASP .NET Web Site Administration Tool.

7. Click Security tab, and to create a user, set the Authentication Type, click Back, and we will be redirected again to the Security page with a link to user creation page. Below is the illustration.

WHY SETTING THE AUTHENTICATION TYPE?  The authentication type we have just set is configured for the web site we have created and has nothing to do with the portal we will be creating. We have only set it to access the Create User link, which is the very purpose of using this tool.

8. Click the Create User link, complete necessary information, then click Create User. With that, we have already created a user which will serve as the Primary Site Administrator in our later steps.

 


End of Part 2 of 4

Forms Authentication in MOSS 2007: IFs and WHYs – Part 1 of 4


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

 

 

 

 

 

Tag Cloud