.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
david stephan
Gaurav Pal
Post New Web Links

SSO to SharePoint through ISAPI extension

Posted By:      Posted Date: October 08, 2010    Points: 0   Category :SharePoint
We have some integration code to enable SSO to SharePoint through ISAPI extension. It worked fine with SharePoint 2007, but with SharePoint 2010, SSO stops working unless SharePoint's anonymous access is enabled.

The key component of the Integration code is an ISAPI extension installed on IIS. This extension uses the user attributes available on the incoming request to get a Kerberos ticket (through S4U2proxy) and impersonate the user through HSE_REQ_EXEC_UNICODE_URL support function.
With anonymous authentication enabled in IIS and our ISAPI extension first on the handler mapping list, we found that we also had to enable SharePoint's anonymous access by following the steps listed in http://blog.drisgill.com/2009/11/sp2010-branding-tip-9-turn-on-anonymous.html; otherwise, users would get prompted for username/password, before our ISAPI extension was even invoked. Note that we didn't need to enable anonymous access for SharePoint 2007.
So the questions are:
1. Is enabling anonymous access the right thing to do? Any security implications? 
2. Why anonymous access needs to be enabled for SP 2010 but not SP 2007?
3. In general, how SharePo

View Complete Post

More Related Resource Links

Visual Studio 2005 Extension for Sharepoint Workflow.


Hi All,

I want to develop sequential workflow using visual studio 2005. I have development server with Windows Server 2003 x86 installed.

Could anyone advise will i need to install Sharepoint first to have workflow feature in visual studio.

Also what all extension component i need to install to develop Sequential Workflow for Sharepoint 2007 document library.


Many Thanks


-- Regards Sandeep

WCF Service hosted inside SharePoint 2010's ISAPI folder and MaxReceivedMessageSize


I got a WCF service hosted inside the SharePoint 2010 following this article http://answers.oreilly.com/topic/1404-how-to-customize-wcf-services-in-sharepoint-2010/

Everything was going great until I wanted to increase the MaxReceivedMessageSize however there is no configuration file for this service.

I tried to add a configuration file to be deployed along with the svc service in the same directory inside the ISAPI mapped folder but I get this error:

The service '/_vti_bin/epcc/messagesarchive/contactssearcher.svc' cannot be activated due to an exception during compilation.  The exception message is: Could not find a base address that matches scheme http for the endpoint with binding BasicHttpBinding. Registered base address schemes are []..

Here is my configuration,

   <service name="WCFServices.ContactsSearcher.ContactsSearcher" behaviorConfiguration="ContactsSearcherBehavior">
    <endpoint address="ContactsSearcher"
    <endpoint address="mex"

Most Common SharePoint Extension Type



I am considering several extension options to overcome some of the limitations of the built-in web services. I looked at custom web services, .wsp solution packages, and web parts. What is the most commonly used extension method by customers? since this will be used by other organizations I'd like to use the most common extension method. Are there other extension options that let me access all sharepoint objects from a remote machine?

Any recommendations/suggestions will be highly appreciated.





SharePoint Extension Type Recommendation



I am considering several extension options to overcome some of the limitations of the built-in web services. I looked at custom web services, .wsp solution packages, and web parts. What is the most commonly used extension method by customers? since this will be used by other organizations I'd like to use the most common extension method. Are there other extension options that let me access all sharepoint objects from a remote machine?

Any recommendations/suggestions will be highly appreciated.



how to add sharepoint extension to my Visual Studio 2010?


Hello Everyone,

I am newbie to Sharepoint currently.What i want to know is that i have a server on which sharepoint is installed and also on that server i have VS2010.When i open my VS on server it has an extension for sharepoint 2007.

in my laptop i have just VS2010 installed.And i have access to the Team Site on that server.I want to develop some webparts and deploy that on server from my laptop(which doesn't have any sharepoint installed in it).

How can i add sharepoint 2007 extension to my VS2010 in order to do my stuff.Is it possible to do so?

Thanks in advance.

Brainstorm your Brain and find solution,if no result stuck to Brainstormer.

The Decorator Pattern & Extension Methods

The decorator pattern provides a formal way to add new functionality to an existing type, without sub-classing. First question: What is wrong with classical inheritance? In and of itself, nothing is wrong with the good old Is-A relationship. It is very common to derive a new class from an existing base class in order to override a few virtual members, and add a pinch of new functionality.

Changing the graphics on the home page of a SharePoint site

When you create a site in Microsoft Windows SharePoint Services by using the default Team Site template, the home page includes two default graphics. A Windows SharePoint Services graphic appears in the body of the page, and a picture of a house in a circle appears near the site title. You can change these graphics to customize your site. Changing the smaller graphic requires a Windows SharePoint Services compatible Web page editor

Displaying SharePoint lists in Web Parts

When you create a built-in or custom list in Microsoft Windows SharePoint Services, Windows SharePoint Services creates a Web Part, a basic building block of a SharePoint site, to display that list. These Web Parts are called List View Web Parts. Windows SharePoint Services stores List View Web Parts in the site collection Web Part gallery. (The site collection Web Part gallery is the most central gallery of Web Parts for a work group. By default, the gallery name is the name of the site, such as "Our Team Site Web Part Gallery." )

Take a tour of your SharePoint site

What is a SharePoint site for?
A SharePoint site is a Web site that provides a central storage and collaboration space for documents, information, and ideas. A SharePoint site is a tool for collaboration, just like a telephone is a tool for communication, or a meeting is a tool for decision making. A SharePoint site helps groups of people (whether work teams or social groups) share information and work together. For example, a SharePoint site can help you:

Coordinate projects, calendars, and schedules.
Discuss ideas and review documents or proposals.
Share information and keep in touch with other people.

Six easy ways to customize your site using Web Parts in SharePoint

Becoming familiar with Web Part customization techniques gives you a range of page-customization choices. For example, you can customize your site's home page so that it displays the specific information that your team needs. You can rearrange the list items on the home page, add lists, and even change the images on the home page. As you become more familiar with Web Part Page customization techniques, you can build interactive Web Part Pages that makes the data in lists more dynamic and useful, and you can add new Web Parts that provide access to external data and Web services.

Working with SharePoint document libraries

Document libraries are collections of files that you can share with team members on a Web based on Microsoft Windows SharePoint Services. For example, you can create a library of common documents for a project, and team members can use their Web browsers to find the files, read them, and make comments. Users with Microsoft Office 2003 can check out and edit the files as if they resided on a local or network drive.

By default, your team Web site comes with a built-in document library named Shared Documents, which is listed on the Quick Launch bar as well as on the Documents and Lists page.

Out of the Depths of SharePoint's XML Hell

I described how a new open source tool called sporm significantly simplifies unit testing SharePoint. Making SharePoint unit testable is my absolute favorite feature of sporm because SharePoint is notoriously hard to unit test. But sporm provides other benefits as well and its ability to pull us out of the depths of verbose loosely typed XML hell and into LINQ excellence is next on my list of favorite features. So in this post I'll describe the pre-sporm technique of querying with CAML, how to query data using sporm, and finally how sporm supports SharePoint's unique architecture of allowing multiple content types per list and what that means to you.

Unit Testing SharePoint - Past, Present, and Sporm

As I described in SharePoint: The Wild West of Software Development there is a serious problem when you develop for SharePoint: ensuring quality through unit testing is really, really hard. And that's where a new open source tool just released today called sporm (SharePoint Object Relational Mapper) comes in. While sporm provides many benefits besides simplified unit testing I wanted to focus on this topic first, because sporm's approach, which models the entity framework in the way it supports POCO's, is a unique feature not available with other SharePoint tools like LINQ to SharePoint.

SharePoint Tutorial - Web Parts

A page in SharePoint is comprised of web parts the exist within zones. Web parts are available for just about everything. For example in the page below there are four web part highlighted by different colors. The purple web part displays a short list of the new announcements stored in the annoucements library. The pink web part displays events from a calendar within the site. The green web part displays an image from a location the user specifies. The gray web part displays a list of links from the links list on the site.

SharePoint Tutorial - Team Sites

Team sites are small web sites that are created to store everything about a particular thing. For example a site can be created for a department in an organization like human resources. I site can be created for a particular project. A site can even be created for a meeting. Everything about the thing (department, project, meeting) like documents, lists, calendars, etc. is stored in that site.

SharePoint Tutorial - Libraries

A library is a feature in SharePoint that stores files (documents). Think of a library as a folder on your file system. For example, a library can be created to store resumes in the human resources team site. A library is usually created for a specific type of file. Libraries can contain metadata to describe the particular file in more detail and to make it easier to find.

SharePoint Tutorial - Lists

A list is a feature in SharePoint that stores a lists of information. For example, a list can be created to store web links in the human resources team site. A list is usually created for a specific type of information. Lists can contain metadata to describe the particular information in more detail and to make it easier to find.
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend