to another application. it is because of this reason claim based authentication has to support single sign on so that it can be used for various scenarios.

Single sign on is very common in window authentication scenarios where users enters their credentials in morning and access lot of resource in their company throught the

day.

With use of kerberos it cannot include all claims like users email address as kerberos is not competent to provide all claims. Also Active directory is key server for company so it is

behind firewall so you cannot access it untill you configure some thing like VPN from outside company network.

Because of above limitation there is need for better flexibility which can override above limitations. Here comes the claims which comes with all possibilities and features

designed to work cross boundaries such as realms, Firewalls and different platforms for secure communications. With claims your application do not need to authenticate

users , it completely decouples from authentication all it needs is security token from the issuer which it trusts. Application will not break if there is change in security

authentication.

The end goal for any claim based architecture is to communicate claims from issuer to application in secure way. Some of the application has goals to enable federation.

There are two type of federation one is with smart client and other is through browser.

When we are using window based application(smart client) then communication is to request token and pass to services(like WCF). When we are using browser based web

application which relies on HTTP get and Post to get and pass security Tokens. For browser based claim aware application it works like Form based authentication. If users

needs to sign in users are redirected to issuer's Login page here the user is authenticated and then redirect to Application. Issues Login Page doesnt neccesarry be  

Login.aspx like in Form Authentication it can be empty html page which is configured in IIS to accept Window authentication, client certificate or smart card etc.

When user is redirected to Issuer Page for Authentication two Important values are passed

as part of query string

1) wa :- Signin or signout to tell issuer if user is logging in or logging off.
2) realm :- The url for the application which is used by Issuer to identify the application.

After authentication, issuer grant the claims configured for that application , package claims into security token and sign it with private key. If application requires claims to

be encrypted it encrypt with public key of application certificate too. After this issuer send the html page to browser with Form tag and security token wrapped inside that.

The action is configured to submit with URL of application it also emit some javascript so that user dont see the page and page is automatically posted to

application url so that application can use security token inside the form tag. Application recieves it and validate the token

and store it in a cookie for subsquent requests.

Now assume if issuer is using Integrated Authentication then user go to application which redirects user to issuer login which post the security token and back to application.

As we know WIF(Windows Identity framework) is used to make any application claim aware. After issuer Post the Authentication token WIF of application takes over. It

listens for "AuthenticateRequest" event and validates the incoming token by using issuer public key to make sure it is trusted with Issuer. It also validate AudienceURI

element to make sure token is issued for correct application. Then it parses the claims in the application create IclaimPrinciple object and assign it to User.Identity in page

life cycle. It also create session token to store these values so that authentication process is not repeated for same session until user sign off or expiration of cookie is done.

On subsequent request session cookie is checked and if values are present then recreate the claim principle using values in cookie

to reassign current user property.

In one of the projects we got a requirement to generate Sequenctial Reference ID's for all infopath forms across sites and thats too without using Code. It means i have form A in a site A and form is submitted so reference ID of that form should come as  1.  After that

another Form B is submitted ,reference ID for that form should be 2 and so on for all forms across sites. We could take sql server help to achieve that functionality but we had to achieve it without using code.

Approach

We created a master list at root level site with just title field in it. Now for every infopath form created in a form library we create a new item in this list using infopath submit connections, and there has to be a unique mapping between each infopath

submitted  form and a item of master list. The title of each item is mapped to one of the field in Infopath Form, so that for every infopath form submitted we can retrieve the corresponding item from master list. The ID of item in master list is taken

as reference ID of infopath form. As ID is always sequential we can take it as reference ID for infopath Form.

Steps

1) Create a Sample Infopath form. We have just created basic form.

 2) DataConnections

   a) SharePoint Library Submit:- This is the usual Submit connection used to submit Infopath Form to a form Library. The Field "frmFormName" is used as form Name in Submit Connection as shown Below.

Where field "frmName" is configured as below :-

b) Data :- This Data connection is recieve data connection(XML File). This XML file is used to pass as paramter in "Web Service Data Connection" which will be described in next point. The content of this XML File is as shown below:-              

<Batch OnError="Continue">
    <Method ID="1" Cmd="New">
        <Field Name='Title'></Field>
    </Method>
</Batch>

c) Web Service Submit:- This Dataconnection is WebService Submit Connection. As i described in approach, we need to create item in Master list for each Form. As we don't have direct way to create item in a list using Infopath forms. We are doing it using webservice Connections. Webmethod "UpdateListItems" from "Lists.asmx" webservice is used to  create item in Master List. This Webmethod(UpdateListItems) require two parameters as a input. First is ListName which is provided by "fldListName" of Infopath Form. Second one is Batch XML which is provided by XMl Dataconnection as shown above.

 This is how Webservice Data Connection is configured. As it is displayedi in Screen shot, UpdateListItems operation take two parameter as input. 1) Name of List in which items needs to be created

2) tns:Updates :- This paramter takes data as XML Format(Which is provided by Secondry Data Connection(Named as Data)). This will contain the values for each field in item. For this Demo we are just passing value of Title Field. Now if you carefully examine the Batch XML which was shown Earlier, Look at this node:-

<Field Name='Title'></Field>

Right now this is empty node i.e. it doesnt contain any value. This XML Node must have to be populated with some value so that item can be created in master list. We will set this value Using Submit Options Rules which will be described later in this section. This value is populated by "frmFormName" field of Infopath Form using Submit Option Rule.

d) MasterFormList :- This is Recieve DataConnection which is used to get reference number of Infopath Form once it is submitted. It will take data from "MasterForm" List.

 and seqNo field will take value from this dataconnection using filter of title field as shown below: -

3) Submit Rules

 There are two submit Rules Configured.

1) Rule 1:- (will execute on this condition When "IsSubmitted= N")[The Default value of IsSubmitted is N ]

     Actions

•    Set Title Field of XML(Secondry Data Connection)

•    Submit WebService Connection
•    Submit SharePoint Library Connection
•    Set IsSubmitted = "Y" (This is used so that this rule will not execute again)

2) Rule 2 (will execute on this condition When "IsSubmitted= Y")

     Actions

•    Submit SharePoint Library Connection

Demo

1)  i opened a new infopath form. Fill it with same value and submitted it.

So a form is submitted and new entry is created in form library as well as in MasterForm list which is used to store all reference ID's. Notice the title of item in Master list this is mapped to "frmFormname" Field of Infopath Form.

Now if i open existing form. it should give me reference ID as "1".

//// Creating Ribbon XML

<CustomAction
   Id="CustomRibbonButton" /// Represent Unique Id of custom action
   Location="CommandUI.Ribbon.ListView" // Represent Location where Ribbon will be visible( I have kept it at List View, for other options you can try out "https://msdn.microsoft.com/en-us/library/bb802730.aspx"
   RegistrationId="0x01003E510038825141608FE2D66FF6804EDD" // Guid of Element specified in Registration type, make sure it is all capital letters, i have seen issues with lowercase letters"
   Rights="EditListItems" // Represent security rights i.e. users who has edit list items will only see this ribbon
   RegistrationType="ContentType"> // Type for which ribbon is attached for e.g. list,content type
    <CommandUIExtension> // Tag for user Interface
      <CommandUIDefinitions> // Represent commands for user interface
        <CommandUIDefinition
         Location="Ribbon.ListItem.Actions.Controls._children"> // Location of RIbbon Tab{ For this example it is under actions tab of list item}
          <Button
           Id="Ribbon.ListItem.Manage.Controls.TestButton"
           Command="ShowAlert" // The command to execute When Button is clicked
           LabelText="Sample Ribbon"// The label to be shown under ribbon
           Image32by32="/_layouts/images/menupersonalize.gif"//The image to shown as ribbon icon
           TemplateAlias="o2" //The TemplateAlias attribute is used to size and position controls within a group when a template is applied to the group. This is used when we have created Group tab and sections for showing ribbons
           Sequence="501" /> // Represent order of placement among other ribbons
        </CommandUIDefinition>
      </CommandUIDefinitions>
      <CommandUIHandlers> // Represent Commands
        <CommandUIHandler
          Command="ShowAlert" // Name should match Command attribute of Button
          CommandAction ="javascript:CustomCommandAction('{SiteUrl}', 'mybutton');" // Javascript function to execute when command(click event of button in this case as defined in button control)
          EnabledScript="javascript:EnableOnSingleItemSelection();" > // Javascript function to execute to enable/disable the ribbon
        </CommandUIHandler>
      </CommandUIHandlers>
    </CommandUIExtension>
  </CustomAction>

// Custom Action to Specify the JS File
<CustomAction
    Id="CustomRibbonButton.Script"
    Location="ScriptLink"
    ScriptSrc ="/_layouts/SampleFolder/js/CustomRibbon.js"/>
</Elements>

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Javascript functions in CustomRibbon.js

var listItem;
var buttonpressed;
var siteURL;

function EnableOnSingleItemSelection() {
    var items = SP.ListOperation.Selection.getSelectedItems();
    var itemsCount = CountDictionary(items);
    return (itemsCount == 1)
}

function CustomCommandAction(siteurl, buttonpressed) {
this.buttonpressed = buttonpressed;  
this.currentSiteUrl = siteurl;
var ctx = SP.ClientContext.get_current();// get client context
    var web = context.get_web();
    var selectedItems = SP.ListOperation.Selection.getSelectedItems(); // Get selected List items
     var listItm = selectedItems[0]; // this will only return ID of list item, to get list object server call has to be mad
      this.listItem = sdlist.getItemById(listItm.id);
        this.spContext.load(this.listItem);// Load listitem in spcontext to fetch all properties of listitem
        this.spContext.load(this.spContext.get_site());// To fetch site properties
        this.spContext.executeQueryAsync(Function.createDelegate(this, this.onQuerySucceeded), Function.createDelegate(this, this.onQueryFailed));
}

/// spContext.executeQueryAsync make asyncronous call to server and return the requested objects, two delegates are attached to handle success(onQuerySucceeded) and faliure(onQueryFailed) operations

function onQuerySucceeded(sender, args) {

 
    var title = this.listItem.get_item('Title');    // get the selected item title
    var options = SP.UI.$create_DialogOptions();
    var siteguid = spContext.get_site().get_id(); // get current site guid
    var itemid = this.listItem.get_item('ID'); // get the selected item id
    var appUrl;  
    appUrl = this.currentSiteUrl + "/_layouts/SampleFolder/SamplePage.aspx?title=" + title + "&siteguid=" + siteguid;// To redirect to SamplePage.aspx with query string parameter as selected item title and current siteguid
  

    options.url = appUrl;
    options.height = 600;
    options.width = 800;  
    options.dialogReturnValueCallback=Function.createDelegate(null, DialogClosedCallback);
    SP.UI.ModalDialog.showModalDialog(options); // To Open Page in Model Dialogue
}
function DialogClosedCallback() {SP.UI.ModalDialog.RefreshPage(SP.UI.DialogResult.OK);} // To refresh the parent  page after model dialogue closes

function onQueryFailed(sender, args) {
    alert('failed ' + args.toString());
}

can customize list view webpart like security settings, view fields, tool bar options etc.  A important point related to List View Webparts is :-

If we set the viewGuid Property of List view webpart to any existing view guid( for e.g default view guid) then copy of that view will be created and attached to list view webpart. Any changes to existing view will not reflect automatically in list view webpart.

//// Here i am creating helper class for defining properties of ListViewWebpart, it will be helpful if you have to configure many list view parts in your solution

public class ListViewWebpartHelper
    {
        private bool _customView = false;
        private  string _query = string.Empty;
        private  string _toolbar = string.Empty;
        private string _authorizationlevel = string.Empty;

//// To Define if we are going to use custom view of default list view of webpart
        public bool customView
        {
            get
            {
                return _customView;
            }
            set
            {
                _customView = value;
            }
        }
        public string  AuthorizationLevel
        {
            get
            {
                return _authorizationlevel;
            }
            set
            {
                _authorizationlevel = value;
            }
        }
           
        public string[] ViewFields  {get;set;}
         
        public string query  {
            get
            {
                return _query;
            }
            set
            {
                _query = value;
            }
        }
        public string toolbar
        {
            get
            {
                return _toolbar;
            }
            set
            {
                _toolbar = value;
            }
        }

    }

//// Set Properties of List View webpart

file URL = "https://sitename/pages/MyPage.aspx"                                           ////    Set Page URL

string[] OCGroup = "UserGroup"//// Set Group Names for which List View Webpart will be visible

helper = new ListViewWebpartHelper();

helper.customView = true;// if needs Custom View

helper.ViewFields = { "Title", "AssignedTo", "StartDate" };// Set Fields which should be visible in List view Webpart

helper.query = string.Format("<GroupBy Collapse=\"FALSE\"><FieldRef Name=\"{0}\"/></GroupBy>","Title");// Set SP Query for View

AddListViewWebPart(web, ListName, "title" URL, "Center", 2, true, helper);

///// Add ListViewWebpart into a Page

<summary>
        /// Adds the list view web part.
        /// </summary>
        /// <param name="web">The web.</param>
        /// <param name="ListName">Name of the list.</param>
        /// <param name="title">The title.</param>
        /// <param name="PageURL">The page URL.</param>
        /// <param name="ZoneID">The zone ID.</param>
        /// <param name="ZoneIndex">Index of the zone.</param>
        /// <param name="publish">if set to <c>true</c> [publish].</param>
        /// <param name="viewHelper">The view helper.</param>
       

 public static void AddListViewWebPart(SPWeb web, string ListName, string title, string PageURL, string ZoneID, int ZoneIndex, bool publish, ListViewWebpartHelper viewHelper)
        {
               SPFile file = web.GetFile(PageURL);
                if (file.CheckOutType == SPFile.SPCheckOutType.None)
                    file.CheckOut();
                string DisplayTitle = string.Empty;
                ListViewWebPart lvw = null;
                bool isDuplicate = false;
                try
                {
                    using (SPLimitedWebPartManager webPartManagerLimited = web.GetLimitedWebPartManager(PageURL, PersonalizationScope.Shared))
                    {
                        lvw = new ListViewWebPart();
                        SPList list = web.Lists[ListName];
                        if (list == null)
                            throw new ArgumentException("List not found ");
                        lvw.ListName = list.ID.ToString("B").ToUpperInvariant();
                        lvw.TitleUrl = list.DefaultViewUrl;
                        lvw.Title = title;
                        lvw.BorderStyle = System.Web.UI.WebControls.BorderStyle.None;
                        lvw.ChromeType = PartChromeType.TitleOnly;
                        if (viewHelper != null && viewHelper.customView)
                        {
                          //// To Set Security settings of View 

if (!string.IsNullOrEmpty(viewHelper.AuthorizationLevel))
                            {
                                lvw.AuthorizationFilter = viewHelper.AuthorizationLevel;

                            }

                            //// To Set View Guid with Default View Guid

if (viewHelper.ViewFields == null || viewHelper.ViewFields.Count() == 0)
                            {
                                lvw.ViewGuid = list.DefaultView.ID.ToString("B").ToUpperInvariant();
                            }
                        }
                        else
                        {
                            lvw.ViewGuid = list.DefaultView.ID.ToString("B").ToUpperInvariant();
                        }
                        foreach (System.Web.UI.WebControls.WebParts.WebPart webpart in webPartManagerLimited.WebParts)
                        {
                            if (webpart.Title == title) / //// To Prevent Duplicates Webparts into a page
                            {
                                isDuplicate = true;
                                break;
                            }
                        }
                        if (!isDuplicate)
                        {
                            webPartManagerLimited.AddWebPart(lvw, ZoneID, ZoneIndex);
                        }
                        list.Update();
                        web.Update();
                        webPartManagerLimited.Web.Dispose();
                    }
////  Override existing view with  Custom Fields  and custom query....

 if (viewHelper != null && viewHelper.customView && !isDuplicate)
                    {
                        using (SPLimitedWebPartManager webPartManagerLimited = web.GetLimitedWebPartManager(PageURL, PersonalizationScope.Shared))
                        {
                            var ViewWebPart = (ListViewWebPart)webPartManagerLimited.WebParts.Cast<System.Web.UI.WebControls.WebParts.WebPart>().FirstOrDefault(w => w.Title.Equals(title));
                            var list = web.Lists[ListName];
                            var view = list.Views.Cast<SPView>().FirstOrDefault(w => w.ID.ToString("B").Equals(ViewWebPart.ViewGuid, StringComparison.OrdinalIgnoreCase));
                            if (viewHelper.ViewFields != null && viewHelper.ViewFields.Count() > 0)
                            {
                                view.ViewFields.DeleteAll();
                                foreach (string field in viewHelper.ViewFields)
                                {
                                    view.ViewFields.Add(field);    ///// Add New fields
                                }
                            }
                            if (!string.IsNullOrEmpty(viewHelper.query))
                                view.Query = viewHelper.query; ///// Set SP Query
                            view.Toolbar = viewHelper.toolbar;
                            view.Update();
                            webPartManagerLimited.Web.Dispose();
                        }
                    }
                }
                finally
                {
                    if (lvw != null)
                        lvw.Dispose();
                    file.CheckIn(string.Empty);
                    if (publish && file.InDocumentLibrary)
                    {
                        file.Publish("Publishing Changes Added");
                        if (file.Item.ModerationInformation != null)
                            file.Approve("Changes are approved");
                    }
                    web.Update();
                }
        }