Archive for the ‘SharePoint2010’ Category

Hello Friends,

It’s been months I haven’t written anything as I was busy with lot of stuff. There are many things to write but starting with topic for which I got many mails from lot of friends through blogs and linked in.

As we all are aware with Claim based in SharePoint 2010 and different option/ways of Authentication( Ldap, Sql, Federation). Claim is the technology of today, In SharePoint 13 Microsoft even removed the Classic  Mode and made it the days of past. Today we will discuss with the form based with LDAP Authentication.

 I will try to provide and exact way to configure Form based authentication in Claim Based Authentication in SharePoint. To enable a form based , web application should be created in Claim based mode only.


Creating a Claims based web application using GUI

  • Go to Application Management in Central admin
  • Go to Manage Web Applications and create a new web application
  • In the option select Claims Based Authentication mode

web app creation1-Ashish Banga

  • In claim authentication types select Enable Windows Authentication and select NTLM
  • In authentication type section for  form based configuring select Enable ASP.NET Membership provider name.

    Note: Membership provider and Role manager name which you provide in this section will be used in everywhere for web config and enabling it. So give it properly and note it for reference.

  • Click on “OK” button to create the web application.
    web app creation2-Ashish Banga
  • web app creation3-Ashish Banga web app creation4-Ashish Banga
  • Now everybody knows web application is nothing until and unless there is at least a single site collection in it. So first create a site collection for it.
  • Go to CA, Application Management, Create site collections
  • Select the appropriate web application
  • Create a site collection with adding appropriate entries .
  • Now the task remain is to modify different web config files and adding user policy for the web application.
Modifying Web.Config files for the FBA web application , Central Administration and Secure Token Service

Note: All the web config entries for copying are provided at end of blog:

In the below web configs (for all ) 3 entries need to be added as per your entry:
1) one for Membership provider and Role manager name
2) Server name
3) Group Container. If you have access to AD you can find the container easily. Go to the AD . Select a user or a group in the container

AD1-Ashish Banga

AD2-Ashish Banga

Modifying web.config of the web application

  • Open the web.config file  of claim based web application’s
  • Find the <membership> entry. There should be only one membership entry and modification should be done in that only. Duplicity will give error.
  • Put the below XML directly under <Providers> entry
  • Find the <roleManager> entry.
  • Put the below XML directly under <Providers> entry.
  • Put the below entry in the People Picker Wildcards entry
    people picker-Ashishbanga

Modifying web.config of the Central Administration site

  • Open web.config file of  Central Administration site
  • Find the <system.web> entry
  • Put the following XML directly below it
  • Put the below entry in the People Picker Wildcards entry
    people picker-Ashishbanga                            


Modifying web.config of the Security Token Service (STS) in 14 Hive

  • Open the web.config file  of Security Token Service (STS)
  • Find the </system.net> entry
  • Below full entry need to be added directly below </system.net> entry
    webconfig-secure store-Ashishbanga

Note: If you more than one SharePoint servers hosting Central Administration or the claims based web application then all web config entries need to be changed in all SharePoint servers.

Add a user policy to the web application

  • Go to CA, Application Management, Manage Web Applications
  • Highlight the claims based web application
  • Click on User Policy and select Add Users link
  • Click the Address Book icon. Type the login name to search. There will be two entries for same name one of AD and other for LDAP
  • Select the account from form authentication one in the User section and click the Add button
  • Give the Full Control access by checking that box. then click the Finish button
    LDAP1-Ashish Banga
    LDAP2-Ashish Banga

Now is the time for testing:

Open your web application in the browser. If all things are done fine. It will open like this:

Claim Based application1-Ashish Banga

Now click on sign in:

Claim Based application2-Ashish Banga

Now Your form based authenticated site will open for you:

Claim Based application3-Ashish Banga

Web config entries

Membership entry:
         <add name=”LdapMember” type=”Microsoft.Office.Server.Security.LdapMembershipProvider, Microsoft.Office.Server, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c” server=”server2008.ashish.com” port=”389″ useSSL=”false” userDNAttribute=”distinguishedName” userNameAttribute=”sAMAccountName” userContainer=”OU=CLAIM,DC=ASHISH,DC=COM” userObjectClass=”person” userFilter=”(ObjectClass=person)” scope=”Subtree” otherRequiredUserAttributes=”sn,givenname,cn” />

Role provider entry:
<add name=”LdapRole” type=”Microsoft.Office.Server.Security.LdapRoleProvider,  Microsoft.Office.Server, Version=, Culture=neutral, PublicKeyToken=71e9bce111e9429c” server=”server2008.ashish.com” port=”389″ useSSL=”false” groupContainer=”OU=CLAIM,DC=ASHISH,DC=COM” groupNameAttribute=”cn” groupNameAlternateSearchAttribute=”samAccountName” groupMemberAttribute=”member” userNameAttribute=”sAMAccountName” dnAttribute=”distinguishedName” groupFilter=”(ObjectClass=group)” userFilter=”(ObjectClass=person)” scope=”Subtree” />

People picker entry:
<clear />
<add key=”AspNetSqlMembershipProvider” value=”%” />
<add key=”LdapMember” value=”*”/>
<add key=”LdapRole” value=”*”/>

Role Manager key for CA:
<roleManager enabled=”true” defaultProvider=”AspNetWindowsTokenRoleProvider” >

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at :https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful

Hope this help

Read Full Post »

Hello Friends,

As discussed in my previous blog the new architecture of Service Application in 2010. Let’s today discuss about connecting two different farms: 

Connecting a service between Publishing and Consuming SharePoint farm

 There are some service applications which have the capability to Publish and which can be used by different SharePoint farms. What that actually means:

We all know Search and crawl is the most intensive task in SharePoint. If a company has 2-3 SharePoint farms and every farms runs its own search/index application. It will be very intensive and time consuming task. Instead of running index in every SharePoint Farm:

We can just do the index in one farm and use that publishing service in different farm. It will save lot of resources and will be very less intensive task.

So what to do next:

As we have other farm where some services are hosted locally as that cannot be published or consumed. So they reside in the same farm and we can consume the search application from the other farm. Below are the steps how to consume the publishing service from other farm:

 Note: To publish or consume the service applications, two farms should be in a far trust.

Once the farm-trust is configured, below are the steps:

Publishing a Service Application

a) Go to a publishing server whose service you want to publish and be used in other farms, open Central Administration.

b) Go to Application Management and then move to è Manage service applications.

c) Click to the right of the service application which you want to publish, clicking on application will open it features be sure to click on its right.

d) On the SharePoint Ribbon, click on Publish. Feature.

e) On the next page check the option “Publish this Service Application to other farms” .

f) Now we have to copy the whole url: It will begin with urn: and ends with .svc.

ex: urn:schemas-microsoft-com:sharepoint:service:ac51d6g73agg

g) Make it ok and proceed.

h) Again do the same step as step C.

i) On the SharePoint Ribbon, click on Publish. Feature.

j) Provide farm Id of the consuming farm, you can find as:   Get-SPFarm | Select Id

k) Add the same.

l) Click the farm id you entered, for the permission.

Now the part of publishing farm is over, we have to enter the url in the consuming farm to use the service:

a) Go to a Consuming server where publishing service needs to be used, open Central Administration.

b) Go to Application Management and then move to manage service applications.

c) On the SharePoint Ribbon, click on Connect.

d) Pass the URL for the service application you have taken in step (f) of publishing server and press OK.

e) Highlight the service application by clicking on it.

f) Here you have an option to can choose, whether or not to include this service application in the default service application group. Click OK once done.

Now when all the stuff is over you can use the service application of a farm just as a locally hosted service application of your farm.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog
Feel free to Rate and provide feedback if you find post useful

Hope this help



Read Full Post »

Friends, Microsoft has release a security bulletin for a FAST Search for SharePoint 2010. PF below for more help.

Full Details available at: http://technet.microsoft.com/security/bulletin/MS13-013

Bulletin ID : MS13-013
Bulletin Name: Vulnerabilities in FAST Search Server 2010 for SharePoint Parsing Could Allow Remote Code Execution (2784242)
Maximum Severity Rating: Important
Vulnerability Impact: Remote Code Execution
Restart Requirement: May require restart
Affected Software: Microsoft FAST Search Server 2010 for SharePoint and Advanced Filter Pack.

General Information

Summary:This security update resolves publicly disclosed vulnerabilities in Microsoft FAST Search Server 2010 for SharePoint. The vulnerabilities could allow remote code execution in the security context of a user account with a restricted token. FAST Search Server for SharePoint is only affected by this issue when Advanced Filter Pack is enabled. By default, Advanced Filter Pack is disabled.

This security update is rated Important for supported editions of FAST Search Server 2010 for SharePoint. For more information, see the subsection, Affected and Non-Affected Software, in this section.The security update addresses the vulnerabilities by updating the affected Oracle Outside In libraries to a non-vulnerable version. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection for the specific vulnerability entry under the next section, Vulnerability Information.

This update is available from the Microsoft Download Center only.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help

Read Full Post »

Friends, As covered in one of my previous blog:

How crawl works in SharePoint ||How indexing work||Basic concept .

We were discussing about ifilters , so How to get these ifilters and what are the various steps need to be taken in the configuration of ifilters? I will work with the example of PDF and the same works for the other types of ifilters or the extension of document which you want in search.

So, to install a PDF ifilters:

  1. Download Adobe PDF Ifilters for 32 & 64 bit platform in MOSS and 64 bit for SharePoint2010.Example Link for pdf version 11 is given below:
  2. Run the setup
  3. When the welcome page comes in, click Next.
  4. When the Software License Agreement page comes, click Accept.
  5. When the Choose Installation Location page comes, click Next.
  6. When the confirmation is displayed that the installation was successful, click OK.

Now to crawl the pdf files with pdf icon images , we have to put the image at SharePoint binary location:

Copy ICPDF.gif(it can be copied from installed files of ifilter) to location drive at which SharePoint Binaries installed: $\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Images.

A PDF extension entry need to be added in SharePoint XML file:

Edit the file \Program Files\Common Files\Microsoft Shared\Web server extensions\12\Template\Xml\DOCICON.XML and put
<Mapping Key=”pdf” Value=”icpdf.gif”/>

Reset IIS to clear the cached settings. It is better to go for iisreset with noforce command: iisreset /noforce

It is pretty necessary to add the file types in the index list, only then the search will work:

  1. On the SharePoint Central Administration home page, Goto Shared Service Provider to open the Shared Services Provider administration site.
  2. On the Shared Services Administration home page, in the Search section, click Search settings.
  3. On the Configure Search Settings page, click File types.
  4. On the Manage File Types page, click New File Type.
  5. On the Add File Type page, in the File extension box, type pdf and click OK.

Note: If the filter for a document is installed after content is indexed, Full crawl on the content indexes need to be done in order to reflect the changes and include PDF documents in search results.

Hope I was able to describe the content correctly based on my knowledge and learning.

If you liked this post, do like on Facebook at: https://www.facebook.com/Ashishsharepointblog

Feel free to Rate and provide feedback if you find post useful
Hope this help

Read Full Post »

Thank You all for your support to give me inspiration . It is the result of this that I have achieved first 1000 Hits in less no of blogs and in very small time.
Thanks to my parents and my friends.


Details of all my Blogs: BlogList







Thank you all very much.


Read Full Post »

Hey Friends,

Today I am here with some concept task . How a search work in SharePoint, but for a search to work SharePoint would first index the content sources.

So, How a crawl work to index the content from MOSS?

Main thing is that it can index, it can crawl anything stored in a server, in any format PDF, Zip, word, excel , txt, HTML, RTF, MS-Office etc. But to index the content other than office or Microsoft the index process is little more complicated but interesting. But the initial or the process is same for all. So let’s have a look on it.

1) When the scheduler for the crawl or index run, it will search for every place you have defined or what you called it a content source.

2) When it find a file in that, it will look on it extension. It will check in SharePoint SSP whether the type is defined to be indexed or not.

3) Now when the SharePoint confirms of file type it will look for a software/Ifilter to read this file. Ifilter is a software which will read a file. Every file need its own ifilter.

4) If SharePoint finds a ifilter for it. It will start opening this file and start scanning the file. It will remove certain words that are not required in search or not need to be indexed ex: 1 ,2 numerals etc.

5) After scanning the whole file it will index the content in index file with the pointer of name and location of the file.

6) Once a file is completed with full process. It will start for next file and with the same process as above.

Now to search or index any file of our use like PDF etc. we need to install the ifilter of every such types, which do not come by default. We can also put the images of such file type in SharePoint images file(12 hive) so that in search document come with their images. :-)

Hope I was able to describe the content based on my knowledge and learning.

Feel free to Rate and provide feedback if you find post useful

Hope this help

Read Full Post »

New Year begins,
Let us pray that it will be a year with new peace, new happiness and abundance of new friends. May the year brings the true example of Humanity.

Let us pray to get the courage to feel the difference of Right and Wrong.
Let us pray for the Delhi Victim girl to Rest in Peace.

Happy New Year.


Read Full Post »

Older Posts »


Get every new post delivered to your Inbox.

Join 107 other followers

%d bloggers like this: