Understanding Sharepoint Custom Claims Provider

CodeProject Before going into any details, we should answer the obvious question.

                                 Why Custom Claims Provider?

Simple ! Claims auth based on Windows based, Forms based or SAML based authentication will generate Claims. But mostly they may not be compatible with the claim information what we / application require.
Below is a claim set generated by STS in case of Claims with Windows.

For example, lets say Date of Birth is part of AD Group, and when user sign in to my site, i will get DOB as one of the claims. But task of my application is to categorize people into Kids (<18 Yrs), Youth (18 to 27), Middle Aged (27 to 40) and so on . . . which will be done by adding one more extra claim with respective values (kids, youth, middle aged . . . ), based on information provided by default claims(Age calculated from DOB). That task will be done by Custom Claim Provider.

Claims Based Authentication in Sharepoint

In this post we will try to understand the basics of Claims Based Authentication in SharePoint.
Lets start this with Claims.

Claim is a piece of information which will authenticate you with in a set of agreed parties.

Let me put it in a simple way for better understanding. If there is a carnival with entrance fee of 100 bucks and all the rides inside are free. When you enter carnival, you pay once and have the ticket with you. Now every time you get on a ride, you just need to show that entrance ticket. The person operating rides will trust the ticket granted by person near entrance.
So, Entrance ticket is the claim you carry.

Access WCF Service Without Service Reference

CodeProject

                                          Change is Inevitable

This absolutely applies to Client Requirements, but not to our code . In other words, the above statement is one of the 3 design principles of Software architecture.

                                System should be Fault Tolerant.

This means, our system should be adoptable for changes and shouldn't break for every reasonable change.
Reason for bringing up this point is a recent situation i undergo.

Uploading Documents Programatically to a Content Organizer Enabled Site

CodeProject We have covered Content Organizer / Metadata Routing in SP2010 in earlier post.
We have created all the required infrastructure for meta data routing or Content organizing. So only task remining is uploading the documents.
Well ! we cannot ask the users to navigate to Drop Off library and upload their documents. Right?
So i have created a simple Webpart for uploading the documents for the specific content type.

 Now we need to upload the selected files programatically to Drop Off Library.

Content Organizer / Metadata Routing in SP2010

CodeProject Clients doesn't bother about content types and sub-sites. All they want is a User-Interface, where they simple upload / download their documents, do some simple tasks.

As a part of Sharepoint application setup or usage, end users will be uploading loads of documents on to the site. So, its our job to make them organized and and easily fectchable.

Content Organizing / Metadata Routing is one of the key Features of Sharepoint 2010, which made developer's and contributer's life easy in this Aspect.

Let me demonstrate the how to configure the Content Organizer for your ease of document management.

Managed Metadata in SP2010 - Simplified

CodeProject

Metadata is data about data.  Well Now you have to tell me wether answer is correct or not? If you understand above definition, the answer is "Correct". The concept of metadata exists from ages, and we have been using it in .net assemblies and many other stuff. Lets take an example of exam report. It will have all the subjects listed and maximum marks, achieved marks, result and grade.  To summarize everything, we call it "Report Card". When you say "Report Card" , it signifies everything mentioned above. So "Report Card" is metadata using which we can classify all the Marks and grades information.

Now lets see what metadata has to do with Sharepoint 2010.

Load Test Using Visual Studio 2010

CodeProject I have been writing code from last 7 years and i hope many of us went through below situation.
We always test our code thouroughly, and will send it for testing expecting zero bugs.
When a tester raised an issue with anything, first thing that comes to our mind is . .

After all the struggle we will make it to Production, and smoke test went awesome.
When the users start using the application . . .  "BOOM"

Webparts in Sharepoint 2010

CodeProject In this post we will see a few commonly used webaprts in Sahrepoint 2010.

1. Content Editor Webpart: This webpart will be used for authoring rich content.This will be available in Media and Content section.

Business Connectivity Services - Architecture

Before comparing BDC vs BSC, one should know that BDC is still a part of SP 2010. It is integral part of Business Connectivity Services (BCS).

One should understand BSC Architecture, before practically implementing it. So, as usually MSDN has everything, and let me bring it on to a post.

Implementing Sandbox Proxy in Sharepoint 2010

CodeProject In earlier post we have seen the Basics and Architecture of Sandbox & Sandbox Proxy.
In this post we will see how to implement one.

A sandbox is a restricted execution environment that enables programs to access only certain resources, and that keeps problems that occur in the sandbox from affecting the rest of the server environment.

Realtime applications will be hosted and executed in Sandbox environment, but its not realistic to complete a project with in scope of a Sandbox execution. There will be many situations where you need to create a file, accessing file system, execute something with Farm Admin credentials.