Archive

Archive for April, 2011

How to wrap a user control inside web part using WSP Builder

April 19, 2011 1 comment

How to wrap a user control inside web part using WSP Builder

Here , I describe a simple way for wrapping ASP.NET user control inside web part for deployment to SharePoint using WSP builder.

1-     Create WSP Project

a-      Firstly, you need to have WSP Builder Package to be deployed on your development environment.

b-     Open visual studio , from File menu, select New -> Project , Select WSPBuilder from project type pane , in the name box type GSWebpart.

2-     Create New WebPart with Feature

a-      In visual studio, Right click on GSWebPart Project, and point to Add, and then click New Item…

b-     In the Categories pane, click WSPBuilder. In the Templates pane, click Web Part Feature. In the Name box, type ConverterWebPart, and then click OK.

c-      In the Feature Settings dialog, type My Web Part for the Title, A web part built using WSPBuilder for the Description and set the Scope to be Site. Click OK.

 

3-     Adding ASP.NET Project Types to the WSPBuilder Project

a-      In visual studio, right click on GSWePart Project , select unload project.

b-     In visual studio, right click on GSWePart Project , select Edit project.

c-      Locate the ProjectTypeGuids element and add the ASP.NET web application project type guid {349C5851-65DF-11DA-9384-00065B846F21}.

d-     Save and then close the GSWePart.csproj file.

e-      Right-click on the GSWePart project and select Reload Project.

f-       Right-click on the GSWePart project and select Properties On the Application tab, change the Target Framework to be .NET Framework 3.5. Save the changes

 

4-     Creating Web User Control

a-      In visual studio, right click on Template Folder, then point to add then select new folder , rename it to CONTROLTEMPLATES.

b-     Right click on CONTROLTEMPLATES folder , then point to add then select new folder , rename it to GSWebPart.

c-       Right-click the GSWebPart folder, select Add then click New Item.

d-     In the Categories pane, click Web. In the Templates pane, click Web User Control. Name the control  ConverterWebPartUserControl.ascx, and then click Add.

e-      Delete the CodeBehind attribute in the ConverterWebPartUserControl.ascx file. Replace the Inherits attribute with GSWebPart. ConverterWebPartUserControl, GSWebPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=[your PublicKeyToken]. The following code shows the corrected file:

f-       <%@ Control Language=”C#” AutoEventWireup=”true” Inherits=” GSWebPart. ConverterWebPartUserControl, GSWebPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=9410bf5b454f3bbd” %>

g-      Open the ConverterWebPartUserControl.ascx file in the designer view. Click the Toolbox, and then add a Label using a drag-and-drop operation. Switch to the code view and rename the ID property to be MyLabel and add “SharePoint” as text property

h-     Open the MyWebUserControl.ascx.cs file and the MyWebUserControl.ascx.designer.cs file. Change the namespace to GSWebPart in both files.

 

 

5-     Wrapping the User Control and Connecting the Properties

This procedure demonstrates how to wrap the user control inside the web part and connect the properties between SharePoint, the web wart and the user control.

To wrap the user control and connect the properties

a-      Open the ConverterWebPart.cs file.

b-     Within the CreateChildControls() method, delete the single line of code under the // Your code here… comment. Enter code to load the MyWebUserControl, assign the value of MyProperty to the DisplayText property of the control and then add the control to the web part’s Controls collection. The code below demonstrates how to do this:

// Your code here…

ConverterWebPartUserControl myControl =

(ConverterWebPartUserControl)Page.LoadControl(“~/_controltemplates/MyWebPart/MyWebUserControl.ascx”);

this.Controls.Add(myControl);

c-      Right-click on the MyWebPart solution and select Rebuild Solution

Advertisements

How to Crawl Open Document Text (odt) files using SharePoint Server 2010?

April 19, 2011 Leave a comment

How to Crawl Open Document Text (odt) files using SharePoint Server 2010?

Open Document Text files can be created by IBM Lotus Symphony. SharePoint Server 2010 can crawl this file types by registering    StarOffice/OpenOffice IFilter .

We can download StarOffice/OpenOffice IFilter from  this site http://www.ifiltershop.com/sofilter.html

Installation Instructions

Setup file is a self-extracting archive that must be downloaded and opened on the machine where you wish to use StarOffice/OpenOffice IFilter.

  1. Stop all appropriate Search services.
  2. Uninstall any previous version of StarOffice/OpenOffice IFilter.
  3. Start setup file and follow the on-screen instructions.
  4. Start all appropriate Search services.
  5. Re-index catalogs containing OpenOffice Writer, Math, Impress, Draw and Calc files.

 

 

Additional Setup Steps

Some Microsoft Search products require additional setup steps as described below:

SharePoint Server 2010:

  1. In SharePoint Central Administration go to “General Application Settings” page
  2. In the “Search” section click on “Farm-Wide Search Administration”
  3. Click on ” Search Service Application” link
  4. On the left side menu select “File Types”
  5. Make sure that “.odt”, “.odp” and all other StarOffice/OpenOffice file types you are planning to index are included

comparison between Search Technologies capabilities for SharePoint 2010

April 18, 2011 Leave a comment

How to Transfer a SharePoint web part Zone into tabs??

April 17, 2011 Leave a comment

How to Transfer a SharePoint web part Zone into tabs??

I do quite a bit of design and implementation on the SharePoint platform. Today, I created a very handy little script that I think might be something worth sharing. I don’t often post anything so specific on my blog, but I found this to be extremely useful, and I hope you do too.

What is it?

This all started with a great idea from the mind of Matthew Koon. If you’re not familiar with SharePoint, one thing you can do in the platform is place web parts on a page, which are akin to sidebar widgets in WordPress or other CMS platforms. Web parts have a lot of nifty drag-and-drop functionality, but the appearance of them is pretty much limited to what you can do with a bit of CSS and maybe some background images. The script that I created transforms a particular “web part zone,” which contains individual web parts, into a jQuery UI tab control. For each web part in the zone, you see an interactive “tab” instead of a boring static box. The contents of each tab is the contents of the web part, itself.

What does it do?

When you’re editing a page, you’ll see this:

When you publish the page, you’ll see this:

1. Attach Required Scripts

You’ll need both jQuery 1.4.2 and jQuery UI 1.8.5 (or later).

2. Attach the Script

Paste this into an attached JavaScript file:

(function($){

$.fn.wpTabify = function(){

if($(‘.ms-WPAddButton’).size() == 0){

return this.each(function(i){

var tabList = $(‘<ul/>’);

var panels = $(‘<div/>’);

$(this).find(‘.s4-wpTopTable,td[id^=”MSOZoneCell_”] > table’).each(function(j){

$(tabList).append(‘<li><a href=”#ui-tab-panel’ + i + j + ‘”>’ + $(this).find(‘h3.ms-WPTitle’).text() + ‘</a></li>’);

var thisPanel = $(‘<div id=”ui-tab-panel’ + i + j + ‘” class=”wpt-ui-tabs-panel”/>’);

var panelContents = $(this).detach();

$(thisPanel).append($(panelContents).find(‘.ms-WPBody’).html());

$(panels).append(thisPanel);

});

if($(tabList).find(‘li’).size() > 0){

$(this).prepend(panels);

$(this).prepend(tabList);

$(this).tabs();

}

});

}

else{

return false;

}

};

})(jQuery);

3. Wrap Your Web Part Zone

In your custom page layout, place a <div/> tag around a web part zone, and give it a class name or ID of your choosing.

<div>

<WebPartPages:WebPartZone id=”zone1″ runat=”server” title=”Tabs Zone”><ZoneTemplate></ZoneTemplate></WebPartPages:WebPartZone>

</div>

4. Run the Script

Now that you’ve attached the script, run it using a jQuery selector that matches the <div> you created in step three (above). This code also goes in an attached JavaScript file.

$(document).ready(function(){

$(‘.my-web-part-tabs‘).wpTabify();

});

5. Add Some Style (Optional)

You may choose to add a bit of style to your newly tabified web parts (this is not specific to this plug-in, these are just some generic jQuery tabs styles):

.ui-tabs-nav {

margin: 0;

padding: 0;

}

.ui-tabs-nav li {

list-style: none;

margin: 0 1px 0 0;

padding: 0;

float: left;

}

.ui-tabs-nav a {

position: relative;

top: 1px;

display: block;

padding: 10px 8px;

border: solid #e1e0dc;

border-width: 1px 1px 0 1px;

background: #d6d6d6;

color: #999;

text-decoration: none;

-webkit-border-top-left-radius: 5px;

-webkit-border-top-right-radius: 5px;

-moz-border-radius-topleft: 5px;

-moz-border-radius-topright: 5px;

border-top-left-radius: 5px;

border-top-right-radius: 5px;

}

.ui-tabs-nav li.ui-tabs-selected a {

color: #c70d37;

background: #fff;

}

.ui-tabs-panel {

clear: both;

padding: 20px;

background: #fff;

border: 1px solid #e1e0dc;

}

.ui-tabs-hide {

display: none;

}

References:-

http://kyleschaeffer.com/sharepoint/wp-tabify/

http://www.thesug.org/Blogs/kyles/Lists/Posts/ViewPost.aspx?ID=8&RootFolder=%2FBlogs%2Fkyles%2FLists%2FPosts

http://archive.msdn.microsoft.com/zonetabs

Configuring claims and forms based authentication for use with an ASP.NET Membership Provider in SharePoint 2010

April 17, 2011 2 comments

                                                                           Forms Based Authentication

1-      Create web application

  • Select Claims Based Authentication
  • Identity Providers
    • Check the Enable Windows Authentication box or you won’t be able to crawl the site
    • Check the Enable ASP.NET Membership and Role Provider checkbox
      * In the Membership provider name edit box, type SqlMember
      * In the Role provider name edit box, type SqlRole
    • Create a new site collection

forms authentication with ASP.NET Provider

2 –      Create Database (aspnetdb) for users:

  • Navigate to C:\Windows\Microsoft .Net\Framework64\v2.0.50727. Locate the aspnet_regsql.exe application and execute it. This will open the windows in the figure below

forms authentication with ASP.NET Provider

  • Click next and choose “Configure SQL server for application services
  • Click next and enter server name and authentication and click next and verify the server information
  • By this you created the aspnetdb now, Now you can populate the SQL Server database with user
  • Click next and enter server name and authentication and click next and verify the server information
  • By this you created the aspnetdb now, Now you can populate the SQL Server database with user information using an application on CodePlex called MembershipSeeder (http://cks.codeplex.com/releases/view/7450#DownloadId=19598). You can proceed with the configuration without usingthe MembershipSeeder application but you will have to manually add users to the aspnetdb tables

1-      Adjust Central Administration web.config

  • Add connection string
    • Locate central administration from IIS and choose Connection String

forms authentication with ASP.NET Provider

  • Add New Connection String  and enter server information and enter “AspNetSqlMembershipProvider” for the connectionString Name

forms authentication with ASP.NET Provider

  • Add Member and Role
    • Open Central administration web.config
    • Locate <system.web> entry and paste the following
    • <roleManager enabled=”true”

         cacheRolesInCookie=”false”

         cookieName=”.ASPXROLES”

         cookieTimeout=”30″z

         cookiePath=”/”

         cookieRequireSSL=”false”

         cookieSlidingExpiration=”true”

         cookieProtection=”All”

         defaultProvider=”AspNetWindowsTokenRoleProvider”

         createPersistentCookie=”false”

         maxCachedResults=”25″>

         <providers>

            <clear />

            <add connectionStringName=”AspNetSqlMembershipProvider”

               applicationName=”/”

               name=”SqlRole”

               type=”System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0,
      Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

            <add applicationName=”/”

               name=”AspNetWindowsTokenRoleProvider”

               type=”System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0,
      Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

         </providers>

      </roleManager>

       

      <membership defaultProvider=”SqlMember”

         userIsOnlineTimeWindow=”15″ hashAlgorithmType=””>

         <providers>

            <clear />

            <add connectionStringName=”AspNetSqlMembershipProvider”

               enablePasswordRetrieval=”false”

               enablePasswordReset=”true”

               requiresQuestionAndAnswer=”true”

               passwordAttemptWindow=”10″

               applicationName=”/”

               requiresUniqueEmail=”false”

               passwordFormat=”Hashed”

               name=”SqlMember”

               type=”System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0,
      Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

         </providers>

      </membership>


    • Double check whether the <membership> and <rolemanager> entries only exist ones. Delete any double entries
    • Locate the <PeoplePickerWildcards> entry and paste the following below it

<clear />

<add key=”AspNetSqlMembershipProvider” value=”%” />

<add key=”SqlMember” value=”%”/>

<add key=”SqlRole” value=”%”/>

4-      Adjust web.config of Security Token Service under Sharpoint  WebServices

  • Add Connection String
    •  Locate Security Token Service from IIS and choose Connection Strings

    • Add New Connection String  and enter server information and enter “AspNetSqlMembershipProvider” for the connectionString Name

forms authentication with ASP.NET Provider

  • Add Role and manager
    • Open STS web.config
    • Add a <system.web> entry directly below the </connectionStrings> and enter the following XML

 <membership>

   <providers>

     <add connectionStringName=”AspNetSqlMembershipProvider”

        enablePasswordRetrieval=”false”

        enablePasswordReset=”true”

        requiresQuestionAndAnswer=”true”

        passwordAttemptWindow=”10″

        applicationName=”/”

        requiresUniqueEmail=”false”

        passwordFormat=”Hashed”

        name=”SqlMember”

        type=”System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0,

Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

   </providers>

</membership>

 

<roleManager enabled=”true”>

   <providers>

      <add connectionStringName=”AspNetSqlMembershipProvider”
applicationName=”/”

         name=”SqlRole”

         type=”System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

   </providers>

</roleManager>

    • Add a </system.web> entry below it

1-      Adjust the web.config of the claims based web application.

  • Add Connection String
    • Locate Security Web application from IIS and choose Connection Strings as before.
    •  Add New Connection String  and enter server information and enter “AspNetSqlMembershipProvider” for the connectionString Name as before.
    •  Locate the <membership> entry
    • Replace everything from <membership> to </membership> with the following XML

<membership defaultProvider=”i”

   userIsOnlineTimeWindow=”15″

   hashAlgorithmType=””>

   <providers>

      <clear />

      <add connectionStringName=”AspNetSqlMemberShipProvider”

         enablePasswordRetrieval=”false”

         enablePasswordReset=”true”

         requiresQuestionAndAnswer=”true”

         passwordAttemptWindow=”10″

         applicationName=”/”

         requiresUniqueEmail=”false”

         passwordFormat=”Hashed”

         name=”SqlMember”

         type=”System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0,

Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

     <add name=”i”

        type=”Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider,

Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />

   </providers>

</membership>

    • Locate the <roleManager> entry
    • Replace everything from <roleManager> to </roleManager> with the following XML

<roleManager enabled=”true”

   cacheRolesInCookie=”false”

   cookieName=”.ASPXROLES”

   cookieTimeout=”30″

   cookiePath=”/”

   cookieRequireSSL=”false”

   cookieSlidingExpiration=”true”

   cookieProtection=”All”

   defaultProvider=”c”

   createPersistentCookie=”false”

   maxCachedResults=”25″>

      <providers>

         <clear />

         <add connectionStringName=”AspNetSqlMemberShipProvider”

            applicationName=”/”

            name=”AspNetSqlRoleProvider”

            type=”System.Web.Security.SqlRoleProvider, System.Web, Version=2.0.0.0,

Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

         <add applicationName=”/”

            name=”SqlRole”

            type=”System.Web.Security.WindowsTokenRoleProvider, System.Web, Version=2.0.0.0,

Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a” />

         <add name=”c” type=”Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider,

Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c” />

   </providers>

</roleManager>

    • Paste the following XML below the PeoplePickerWildcards entry

<clear />

<add key=”AspNetSqlMembershipProvider” value=”%” />

<add key=”SqlMember” value=”%”/>

<add key=”SqlRole” value=”%”/>

6-     Add a user policy to the web application

  • Go to Central Administration
  • Go to Application Management
  • Click on Manage Web Applications
  • Select the claims based web application
  • Click on User Policy
  • Click on the Add Users link
  • Click the Next button.
  • Click the Address Book icon.
  • Type in the NT login name or account name and click the search button. If it’s working correctly you should see at least two entries for the account – one that is for the user’s Active Directory account, and one that is for that same account but which was found using the LDAP provider.
  • Select the account in the User section and click the Add button
  • Click the OK button
  • Check the Full Control checkbox, then click the Finish button

forms authentication with ASP.NET Provider



Configuring claims and forms based authentication for use with an LDAP provider in SharePoint 2010

April 17, 2011 4 comments

Configuring claims and forms based authentication for use with an LDAP provider in SharePoint 2010

Using an LDAP provider with forms based authentication means that users will use their Windows or AD account to log in. However, because forms based authentication will be used they don’t get the usual popup, but they will use a sign-in page to log in.
How to set up forms based authentication while using an LDAP provider?
When you want to create your web application:-
1) Select Claims Based Authentication and Identity Providers: –
* Check the Enable Windows Authentication box or you won’t be able to crawl the site
* Check the Enable ASP.NET Membership and Role Provider checkbox
– In the Membership provider name edit box, type LdapMember.
– In the Role provider name edit box, type LdapRole.

2) Create a new site collection.
3) Adjust the web.config of the Central Administration site:-
* Open the Central Administration site’s web.config file
* Find the entry

<membership>

   <providers>

      <add name=”LdapMember”

         type=”Microsoft.Office.Server.Security.LdapMembershipProvider,
 Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral,
 PublicKeyToken=71e9bce111e9429c”

         server=”SERVER NAME”

         port=”389″

         useSSL=”false” 

userDNAttribute=”distinguishedName”

         userNameAttribute=”sAMAccountName”

         userContainer=”OU=SPUsers,DC=sharepoint,DC=com”

         userObjectClass=”person”

         userFilter=”(ObjectClass=person)”

         otherRequiredUserAttributes=”sn,givenname,cn” />

   </providers>

</membership>

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

   <providers>

      <add name=”LdapRole”

         type=”Microsoft.Office.Server.Security.LdapRoleProvider,
Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c”

         server=” SERVER NAME”

         port=”389″

         useSSL=”false”

         groupContainer=”OU=SPUsers,DC=sharepoint,DC=com”

         groupNameAttribute=”cn”

         groupNameAlternateSearchAttribute=”samAccountName”

         groupMemberAttribute=”member”

         userNameAttribute=”sAMAccountName”

         dnAttribute=”distinguishedName”

         groupFilter=”(ObjectClass=group)”

         userFilter=”(ObjectClass=person)”

         scope=”Subtree”  />

   </providers>

</roleManager>

Note:
The user and group containers are the containers in AD where the users and groups you want to use for authentication reside:-
• Go to the domain controller
• Open Active Directory Users and Computers
• Select a user or a group in the container
• Right click and select All Tasks => Resultant Set Of Policy (Planning)
• Click the browse button next to Container and select the container
• This will give you the path to the container
4) Check whether the and entries only exist ones. Delete any double entries.
5) Edit the entry

<clear />
      <add key="AspNetSqlMembershipProvider" value="%" />
      <add key="LdapMember" value="*"/>
  <add key="LdapRole" value="*"/>

6) Adjust the web.config of the Security Token Service (STS) virtual directory:-
* Open the Security Token Service (STS) virtual directory’s web.config file
* Find the entry
* Add a </system.web>  entry directly below it

<membership>

   <providers>

      <add name=”LdapMember”

         type=”Microsoft.Office.Server.Security.LdapMembershipProvider,
 Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c”

server=”SERVER NAME”

         port=”389″

         useSSL=”false”

         userDNAttribute=”DISTINGUISHEDNAME”

         userNameAttribute=”SAMACCOUNTNAME”

         userContainer=”OU=SPUSERS,DC=SHAREPOINT,DC=COM”

         userObjectClass=”person”

         userFilter=”(ObjectClass=person)”

         otherRequiredUserAttributes=”SN,GIVENNAME,CN” />

   </providers>

</membership>

<roleManager enabled=”true”>

   <providers>

      <add name=”LdapRole”

         type=”Microsoft.Office.Server.Security.LdapRoleProvider,
 Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c”

         server=” SERVER NAME”

         port=”389″

         useSSL=”false”

         groupContainer=”OU=SPUSERS,DC=SHAREPOINT,DC=COM”

         groupNameAttribute=”cn”

         groupNameAlternateSearchAttribute=”SAMACCOUNTNAME”

         groupMemberAttribute=”member”

         userNameAttribute=”SAMACCOUNTNAME”

         dnAttribute=”DISTINGUISHEDNAME”

         groupFilter=”(ObjectClass=group)”

         userFilter=”(ObjectClass=person)”

         scope=”Subtree” />

   </providers>

</roleManager>

*Add a </system.web>  entry directly below it

7) Adjust the web.config of the claims based web application
* Locate the <Providers> entry
* Edit the following XML directly below the entry

<add name=”LdapMember”

   type=”Microsoft.Office.Server.Security.LdapMembershipProvider,
Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral,
 PublicKeyToken=71e9bce111e9429c”

   server=” SERVER NAME”

   port=”389″

   useSSL=”false”

   userDNAttribute=”DISTINGUISHEDNAME”

userNameAttribute=”SAMACCOUNTNAME”

   userContainer=”OU=SPUSERS,DC=SHAREPOINT,DC=COM”

   userObjectClass=”person”

   userFilter=”(ObjectClass=person)”

   otherRequiredUserAttributes=”SN,GIVENNAME, CN” />

* Edit  <roleManager>  the entry

<add name=”LdapRole”

   type=”Microsoft.Office.Server.Security.LdapRoleProvider,
Microsoft.Office.Server, Version=14.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c”

   server=” SERVER NAME “

   port=”389″

   useSSL=”false”

   groupContainer=”OU=SPUsers,DC=sharepoint,DC=com”

   groupNameAttribute=”cn”

   groupNameAlternateSearchAttribute=”samAccountName”

   groupMemberAttribute=”member”

   userNameAttribute=”sAMAccountName”

   dnAttribute=”distinguishedName”

   groupFilter=”(ObjectClass=group)”

   userFilter=”(ObjectClass=person)”

   scope=”Subtree” />

8) Edit the <PeoplePickerWildcards> entry

<clear />
      <add key="AspNetSqlMembershipProvider" value="%" />
      <add key="LdapMember" value="*"/>
  <add key="LdapRole" value="*"/>

9) Add a user policy to the web application
* Go to Central Administration
* Go to Application Management
* Click on Manage Web Applications
* Select the claims based web application
* Click on User Policy
* Click on the Add Users link
* Click the Next button.
* Click the Address Book icon.
* Type in the NT login name or account name and click the search button. If it’s working correctly you should see at least two entries for the account – one that is for the user’s Active Directory account, and one that is for that same account but which was found using the LDAP provider.
* Select the account in the User section and click the Add button
* Click the OK button
* Check the Full Control checkbox, and then click the Finish button.

References:-
http://www.sharepointchick.com/archive/2010/05/06/configuring-claims-and-forms-based-authentication-for-use-with-an.aspx

http://blogs.technet.com/b/speschka/archive/2009/11/05/configuring-forms-based-authentication-in-sharepoint-2010.aspx
http://kbochevski.blogspot.com/2011/01/setup-fba-for-sharepoint-2010-using-vs.html

change service accounts and service account passwords in SharePoint Server 2007

April 16, 2011 2 comments

How to change service accounts and service account passwords in SharePoint Server 2007 and in Windows SharePoint Services 3.0

To change the passwords for service accounts in Microsoft office SharePoint server 2007 and in Microsoft Windows SharePoint Services 3.0, we need to do steps with stsadmin commands and through Central Administration Web Site.

Let us do simulation with complete example, the following table contains farm servers

Server Name Server Role
WebFront1 Webfrontend server, Query Server
WebFront2 Webfrontend server, Query Server
Index1 Host Central Administration Site, Indexer
SQL1 Clustered Database
SQL2

We need to change the password for accounts that run central administration service, office SharePoint search service, and SSP.

As I mentioned in the above table, Index 1 server hosts (central administration role), also play as indexer. So we need to update services account password as the following:-

1-   Update the password for the account that is used by the Central Administration application pool. To do this, follow these steps:

a-   On all servers in the server farm, open a command prompt, type the following line, and then press ENTER:

cd %commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin

b-   On the server that hosts the Central Administration Web site, type the following line at the command prompt, and then press ENTER:

stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword

c-   On all other servers in the server farm, type the following line at the command prompt, and then press ENTER:

stsadm -o updatefarmcredentials -userlogin DomainName\UserName -password NewPassword -local

d-   Restart Microsoft Internet Information Services (IIS) 6.0. To do this, type the following line at the command prompt, and then press ENTER:

iisreset /noforce

2-    Verify that the Administration Application Pool Credential Deployment job definition is no longer displayed on the Timer Job Definitions page of SharePoint 3.0 Central Administration. To do this, follow these steps:

a-    Open SharePoint 3.0 Central Administration, click Operations, and then click Timer job definitions under Global Configuration.

b-   Verify that the Administration Application Pool Credential Deployment job definition is no longer displayed in the list.

Note If the Administration Application Pool Credential Deployment job definition is displayed in the list, wait until it disappears from the list.

WebFront1 and WebFront2 servers play Query Role and hosts web applications . So we need to update the password of the application pool account that is used by Web applications on the server farm, the password for the account that is used by every Shared Services Provider (SSP) on the server farm, and for the account that is used to run the Office SharePoint Server Search service as the following:-

1-   Update the password for the application pool account that is used by Web applications on the server farm. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:

stsadm -o updateaccountpassword -userlogin DomainName\UserName -password NewPassword –noadmin

2-   Update the password for the account that is used by every Shared Services Provider (SSP) on the server farm. To do this, type the following line at a command prompt on every server on the server farm, and then press ENTER:

stsadm.exe -o editssp -title SharedServicesProviderName -ssplogin DomainName\UserName -ssppassword NewPassword

3-   Update the password for the account that is used to run the Office SharePoint Server Search service. To do this, type the following line at the command prompt, and then press ENTER:

stsadm.exe -o osearch -farmserviceaccount DomainName\UserName -farmservicepassword NewPassword

4-   Update the password for the default content access account that is used by the Office SharePoint Server Search service. To do this, follow these steps:

a-   Open SharePoint 3.0 Central Administration, and then click the link to the SSP Web application under Shared Services Administration.

b-   Under Search, click Search settings, and then click Default content access account.

c-   Specify the password to use for the content access account, and then click OK.

Refernces:-

http://support.microsoft.com/kb/934838