SharePoint Foundation 2010:
kb2266423 – Download

SharePoint Server 2010:
kb2352342 (not live yet) – Download

(Updated to point the urls to the correct hotfixes)

via:
http://blogs.msdn.com/b/aaronsaikovski
http://blogs.technet.com/b/stefan_gossner

Download the zipped Twitter.OSDX and add it to your Federated Search Locations and enjoy searching in twitter! ( I presume you know how to add a Federated Search Results Webpart to your Search Center ).

• Create a Custom Security Token Service with the Windows Identity Framework SDK

In this post I will cover:

• Create a Custom SPClaimProvider
• Register your Custom SPClaimProvider

Create a Custom SPClaimProvider

For SharePoint 2010 to Trust any Identity Provider, we need a SPClaimProvider specific for that provider. This SPClaimProvider has two main purposes:

• Provide a way for SharePoint to communicate with any Trusted Identity Provider in a uniform (Interface) way.
• And provide SharePoint a way to use the same Claims for Users that have logged in through a different (e.g. AD) Identity Provider, let’s call this Claims Augmentation

To create a SPClaimProvider follow the following steps:

• Create a new VS2010 Empty SP2010 Project
• And add references to Microsoft.IdentityModel, Microsoft.SharePoint and Microsoft.SharePoint.Security.
• Create a new Class, let’s name it CustomClaimsProvider and inherit from:Microsoft.SharePoint.Administration.Claims.SPClaimProvider
• Implement all the methods for resolving claims, this is so we can use the claims provided within SharePoint to give rights to claims:
  • FillHierarchy
  • FillResolve
  • FillSearch, FillSchema
  • FillClaimTypes,FillClaimValueTypes,FillEntityTypes
• Implement GetClaimsForEntity for the claims augmentation
• Override the SupportsEntityInformation,SupportsHierarchy,,SupportsResolve and SupportsSearch properties and let them “return True” since we have implemented all the Fill Methods for this SPClaimProvider
• Give your Provider a Name by overriding the Property Name. You will need this later on.

In fairness, this post has an excellent description on the subject also.
Sample implementation of FillClaimsForEntity

/// <summary>
/// Get's the username part of a claims authentication login claim
/// figure out who the user is so we know what team to add to their claim
/// the entity.Value from the input parameter contains the name of the
/// authenticated user.  for a SQL FBA user, it looks something like
/// 0#.f|sqlmembership|user1; for a Windows claims user it looks something
/// 0#.w|steve\\wilmaf
/// 0#.t|Customsleden|stef@tamtam.nl
/// </summary>
/// <param name="identityClaims"></param>
/// <returns>only the login part</returns>
public static string GetLoginPartFromIdentityClaim(string identityClaims) {
    string login = identityClaims;
    if (!string.IsNullOrEmpty(login) && login.Contains("|")) {
        string[] parts = login.Split('|');
        if (parts.GetLength(0) == 3) // formsbased or trusted provider based
            login = parts[2];
        if (parts.GetLength(0) == 2) // windows based
            login = parts[1];
    }
    return login;
}

/// <summary>
/// Add Claims to a logged in User, from Dynamics CRM info
/// </summary>
/// <param name="context">Current Context, url</param>
/// <param name="entity">the logged in user/claim</param>
/// <param name="claims">The list of claims for the user</param>
protected override void FillClaimsForEntity(Uri context, SPClaim entity, List<SPClaim> claims) {
    if (claims == null)
        throw new ArgumentNullException("claims");
    if (entity == null)
        throw new ArgumentNullException("entity");

    Logging.LogMessage(entity.Value);

    string login = Utilities.GetLoginPartFromIdentityClaim(entity.Value);

    // if windows user, get the email ?
    if (!string.IsNullOrEmpty(login)) {
        Logging.LogMessage(string.Format("User is {0}", login));

        CRMClient.Entities.User user = null;
        string email = login;
        if (login.Contains("@")) {
            user = CRMClient.CrmSQLClient.GetUserByEmail(login);
        }
        if (login.Contains("\\")) {
            user = CRMClient.CrmSQLClient.GetUser(login);
            if (user != null)
                email = user.Email;
        }
        // employee, crm users
        if (user != null) {
            try {
                Logging.LogMessage(string.Format("User is SystemUser of CRM with an license, Name:{0}", user.FullName));

                claims.Add( GetClaim(CustomClaimsProvider.CustomAccountTypeClaimType, "everyone"));

                SPClaim employee = null;
                if (user.FullLicense) { // admin and or full license
                    employee = GetClaim(CustomClaimsProvider.CustomAccountTypeClaimType, "employee");
                }
                else {// readonly
                    employee = GetClaim(CustomClaimsProvider.CustomAccountTypeClaimType, "employeero");
                }
                if (employee != null)
                    claims.Add(employee);
            }
            catch (Exception exc) {
                Logging.LogException(exc);
            }
        }
        else {
            Logging.LogMessage(string.Format("{0} not found as SYSTEMUSER in CRM", login));
        }
    }
}

Register your Claims Provider for SharePoint

In order for your Claims Provider to be registered within SharePoint 2010 you will need to create a specific type of Feature.

• Add a Farm Feature to your Project
• Add an EventReicever to your new Feature
• And let your receiver inherit from SPClaimProviderFeatureReceiver (see: Register)
• And now implement the following Properties in your Feature Event Receiver
  • ClaimProviderDisplayName
  • ClaimProviderDescription
  • ClaimProviderAssembly
  • ClaimProviderType

You can use this to return the last two properties:

/// <summary>Get the Full Assembly Name of the Claim provider we want to register</summary>
public override string ClaimProviderAssembly {
    get {
        return typeof(CustomClaimsProvider).Assembly.FullName;
    }
}

/// <summary>Get the Class Type of the Claim provider we want to register</summary>
public override string ClaimProviderType {
    get {
        return typeof(CustomClaimsProvider).FullName;
    }
}

That’s it, you can now register your Claims Provider, and if you want you can use this as is.
Next post will be on these subjects:

• Create a Trust between your Tusted Identity Provider (STS) and SharePoint 2010
• Create or Configure your SP2010 WebApplication to use the Tusted Identity Provider

write-host -f Green "Add solution: TamTam.SP2010.PDFIcon.wsp"
Get-ChildItem TamTam.SP2010.PDFIcon.wsp | Add-SPSolution
write-host -f Green "Install solution: TamTam.SP2010.PDFIcon"
Install-SPSolution -Identity "TamTam.SP2010.PDFIcon.wsp" -GacDeployment

Here is the code from the solution to add the PDF Icon xml element to the DOCICON.xml and to all the Search Applications of the Farm. I also added the removal code in the FeatureDeactivating code in the solution itself!

public class PDFIconEventReceiver : SPFeatureReceiver {

    /// <summary>Const of the docicon FileName</summary>
    private const string dociconFile = "TEMPLATE\\XML\\DOCICON.xml";

    /// <summary>
    /// Handle the activation of the feature for the PDF Icon for SP2010,
    /// Adds an entry to the SharePoint DOCICON.xml file for the PDF Icon in this solution
    /// </summary>
    /// <param name="properties"></param>
    public override void FeatureActivated(SPFeatureReceiverProperties properties) {

        string dociconXmlFile = string.Format("{0}\\..\\..\\..\\{1}",
            properties.Feature.Definition.RootDirectory,
            dociconFile);

        XmlDocument docicon = new XmlDocument();
        docicon.Load(dociconXmlFile);

        // locate existing PDF icon
        XmlNode pdfnode = docicon.SelectSingleNode("//DocIcons/ByExtension/Mapping[@Key='pdf']");
        if (pdfnode == null) {
            // no existing PDF icon found, add to the file:
            XmlNode rootextentionNode = docicon.SelectSingleNode("//DocIcons/ByExtension");
            if (rootextentionNode != null) {
                // add new Mapping
                pdfnode = docicon.CreateElement("Mapping");

                XmlAttribute key = docicon.CreateAttribute("Key");
                // extention for this mapping
                key.Value = "pdf";
                pdfnode.Attributes.Append(key);

                XmlAttribute value = docicon.CreateAttribute("Value");
                // url of this solution's pdf icon image
                value.Value = "TamTam.SP2010.PDFIcon/pdficon_small.gif";
                pdfnode.Attributes.Append(value);

                rootextentionNode.AppendChild(pdfnode);
                // save new docicon file to disk
                docicon.Save(dociconXmlFile);
            }
        }
        // add the PDF Icon to the SearchApplications
        foreach (SearchServiceApplication service in SearchService.Service.SearchApplications) {
            // open the Content
            Content content = new Content(service);
            // register the icon as an Extention
            try { content.ExtensionList.Create("pdf"); }
            catch { }
        }
    }
}

The short version is, you can use this in you deploy script to do Web.Config modifications

Example for an AppSettings Configuration Key:”

Add-WebConfiguration /appSettings "IIS:\sites\Default Web Site" -atIndex 0 -Value @{key="DBConnectionString";value="server=10.2.34.1"}

This will result in the following addition of your Web.Config.

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <appSettings>
        <add key="DBConnectionString" value="server=10.2.34.1" />
    </appSettings>
</configuration>

Note: Be carefull with ANY Web.Config modification, you can break stuff!
Load the WebAdministration module in powershell:

#load webadministration powershell module
$hasSnapin = get-pssnapin | Select { $_.Name.toLower().Trim() = "webadministration" }
if ($hasSnapin -ne $null) {
  # IIS7 / Windows 2008
  add-pssnapin WebAdministration
} else {
  # IIS7.5 / Windows 2008 R2
  import-module WebAdministration
}

1. Create a Page ContentType

Add a New ContentType to your project. VS 2010 will ask you from which ContentType you want to inherit, select Article Page.
You will get a new ContentTypeId!
Supply a Name, Group and Description for your Page ContentType.

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <!-- Parent ContentType: Article Page (0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D) -->
  <ContentType ID="0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D00d77cd9769a6443cd8dce93ee832e8303"
               Name="CustomPageContentType"
               Group="Site Content Types"
               Description="My Page Content Type"
               Inherits="TRUE"
               Version="0">
    <FieldRefs>
      <!-- Supply fields here -->
    </FieldRefs>
  </ContentType>
</Elements>

Add the (Publishing) Fields you want to use in your Publishing Pages.

2. Provision a MasterPage

Now add an empty Module, name it MasterPages and remove the sample.txt.
Add your Site.Master page to your newly created module
Open the Element.xml of your module
Apply the following changes:

• Add RootWebOnly=”TRUE” to you Module
• Add a Title to your File
• Add a Description to your File
• Add a ContentType to your File with the value $Resources:cmscore,contenttype_masterpage_name;, cause this is a masterpage!

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <!-- Mind the RootWebOnly attibute here -->
  <Module Name="MasterPages" Url="_catalogs/masterpage" RootWebOnly="TRUE">
    <File Path="PageLayouts\Site.master" Url="Ordina.master" Type="GhostableInLibrary" >
      <!-- Required -->
      <Property Name="Title" Value="Site Master Page" />
      <!-- optional -->
      <Property Name="MasterPageDescription" Value="Master Page for Site" />
      <!-- optional -->
      <Property Name="PublishingPreviewImage" Value="" />
      <!-- Required and important, leave this value like this (MasterPage) -->
      <Property Name="ContentType" Value="$Resources:cmscore,contenttype_masterpage_name;" />
    </File>
  </Module>
</Elements>

3. Provision a Publishing PageLayout

Add your PageLayout to either a new Module or the MasterPage Module. If you create a new Module, don’t forget to add the RootWebOnly=”TRUE”.

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <!-- Mind the RootWebOnly attibute here -->
  <Module Name="PageLayouts" Url="_catalogs/masterpage" RootWebOnly="TRUE">
    <File Path="PageLayouts\PageLayout.aspx" Url="PageLayouts/PageLayout.aspx" Type="GhostableInLibrary" >
      <!-- Required -->
      <Property Name="Title" Value="Site WelcomePage" />
      <!-- Optinal -->
      <Property Name="MasterPageDescription" Value="Description" />
      <!-- Required and important, leave this value like this, THIS IS A PageLayout! -->
      <Property Name="ContentType" Value="$Resources:cmscore,contenttype_pagelayout_name;" />
      <!-- Required and important and use your CustomPageContentType ContentTypeId here ! -->
      <Property Name="PublishingAssociatedContentType"
                Value=";#CustomPageContentType;#0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D00d77cd9769a6443cd8dce93ee832e8303;#"/>
      <!-- Optional, add default webpart(s) to zones -->
      <AllUsersWebPart WebPartZoneID="WebPartZoneTop" WebPartOrder="1">
        <![CDATA[ WebPart XML here ]]>
      </AllUsersWebPart>
    </File>
  </Module>
</Elements>

You can also add “default” WebParts to you page layout with the AllUsersWebPart tag.

4. Provision a Publishing Page

And you can even provision Publishing Pages with a module.
Now add an empty Module, name it DefaultPages and remove the sample.txt.
Open the Element.xml of your module
I have provided a sample here, please note the following:

• Use the ContentTypeBinding to bind your CustomPageContentType to the Pages list
• Use the default.aspx from the default SharePoint Site Definition SPS by adding the SetupPath attribute to your Module (more here).
• You can provision WebParts and Field Values
• To deploy multiple Publishing Pages add another File ellement, and change the Url attribute of the File Element, to create another page.
• You can use the feature to provision Pages from within you Onet.xml, but don’t forget to activate dependand features first ( Publishing Infrastructure, Publishing, optional ContentTypes )

<?xml version="1.0" encoding="utf-8"?>
<Elements xmlns="http://schemas.microsoft.com/sharepoint/">
  <!-- Add your CustomPageContentType ContentTypeId to the Pages List -->
  <ContentTypeBinding ContentTypeId="0x010100C568DB52D9D0A14D9B2FDCC96666E9F2007948130EC3DB064584E219954237AF3900242457EFB8B24247815D688C526CD44D00d77cd9769a6443cd8dce93ee832e8303"
                      ListUrl="Pages" />
  <Module Name="ProvisionDefaultPages" Url="$Resources:osrvcore,List_Pages_UrlName;"
          SetupPath="SiteTemplates\SPS" >
    <!-- Note the Url of this File element -->
    <File Path="default.aspx" Url="default.aspx" Type="GhostableInLibrary">
      <!-- Required -->
      <Property Name="Title" Value="HomePage" />
      <!-- Required, Use the ContentType CustomPageContentType you created earlier ! -->
      <Property Name="ContentType" Value="CustomPageContentType" />
      <!-- Required, Use the PageLayout you created earlier -->
      <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/PageLayout.aspx, Site WelcomePage" />
      <!-- Optional Extra attributes -->
      <Property Name="PublishingPageContent" Value="WebContent field value" />
      <!-- Optional, add default webpart(s) to zones -->
      <AllUsersWebPart WebPartZoneID="WebPartZoneTop" WebPartOrder="1">
        <![CDATA[ WebPart XML here ]]>
      </AllUsersWebPart>
    </File>
    <!-- Note the Url of this File element -->
    <File Path="default.aspx" Url="anotherpage.aspx" Type="GhostableInLibrary">
      <!-- Required -->
      <Property Name="Title" Value="Another Page" />
      <!-- Required, Use the CustomPageContentType ContentType you created earlier -->
      <Property Name="ContentType" Value="CustomPageContentType" />
      <!-- Required, Use the PageLayout you created earlier -->
      <Property Name="PublishingPageLayout" Value="~SiteCollection/_catalogs/masterpage/PageLayout.aspx, Site WelcomePage" />
      <!-- Optional Extra attributes -->
      <Property Name="PublishingPageContent" Value="WebContent field value" />
      <!-- Optional, add default webpart(s) to zones -->
      <AllUsersWebPart WebPartZoneID="WebPartZoneTop" WebPartOrder="1">
        <![CDATA[ WebPart XML here ]]>
      </AllUsersWebPart>    </File>
  </Module>
</Elements>

5. Small bonus tip

When you deploy MasterPages and PageLayouts through features, they become part of the site collection. You provision these files in the _catalog/MasterPages SPList of your Site Collection! Now default SharePoint won’t load the contents of your deployed masterpages and pagelayouts into the actual ContentDb. It only uses a reference in the ContentDb to the actual file on Disk in your Feature folder. So updating these PageLayouts and MasterPages can be done by uploading a new Solution with the updated Files.
But user’s can change files in the Site Collection through SharePoint Designer. If a User Customizes a MasterPage or PageLayout, it becomes Customized or Un-Ghosted. This means the file contents are now stored in the ContentDb! And when you re-deploy your solution with your new feature and files (update the feature version number!) you would expect to see your changes, but you won’t!

You can use the object model to undo this, Re-Ghosting, by calling the RevertContentStream() on the SPFile of your PageLayout or MasterPage.
I have written a method for that which you can call from the Feature Event Receiver Activate and Upgrade (version number of your feature ):

    /// <summary>
    /// This class handles events raised during feature activation, deactivation, installation, uninstallation, and upgrade.
    /// </summary>
    /// <remarks>
    /// The GUID attached to this class may be used during packaging and should not be modified.
    /// </remarks>
    [Guid("fa5fdea4-f3be-4b17-8942-528517b2e28c")]
    public class ProvisioningEventReceiver : SPFeatureReceiver {

        public override void FeatureActivated(SPFeatureReceiverProperties properties) {
            UpdateFilesForFeature(properties);
        }

        //public override void FeatureDeactivating(SPFeatureReceiverProperties properties)
        //{
        //}

        public override void FeatureUpgrading(SPFeatureReceiverProperties properties, string upgradeActionName, System.Collections.Generic.IDictionary<string, string> parameters) {
            UpdateFilesForFeature(properties);
        }

        /// <summary>
        /// Update files for a Feature, based on defaults and file extentions.
        /// </summary>
        /// <param name="feature">The feature</param>
        public static void UpdateFilesForFeature(SPFeatureReceiverProperties feature) {
            // locate the webpart and dwp file for this feature
            string layoutdirectory = feature.Definition.RootDirectory;
            if (!layoutdirectory.EndsWith("/"))
                layoutdirectory += "/";
            layoutdirectory += "PageLayouts";

            string[] featurefiles = System.IO.Directory.GetFiles(layoutdirectory);

            List<string> featurefilesList = new List<string>();
            foreach (string filename in featurefiles) {
                string ext = System.IO.Path.GetExtension(filename).ToLowerInvariant();

                if (ext.EndsWith("aspx") || ext.EndsWith("master") || ext.EndsWith("xml"))
                    featurefilesList.Add(System.IO.Path.GetFileName(filename).ToLowerInvariant());

                Logging.LogMessage("added to list: " + filename);
            }

            if (featurefilesList.Count > 0) {
                Logging.LogMessage("no files found");
                SPSite site = Base.Feature.GetActivationSite(feature);
                if (site != null) {
                    // locate the masterpages/page layouts list
                    SPList masterpagegallery = null;

                    foreach (SPList list in site.RootWeb.Lists) {
                        if (list.BaseTemplate == SPListTemplateType.MasterPageCatalog) {
                            masterpagegallery = list;
                            break;
                        }
                    }
                    if (masterpagegallery != null) {
                        Logging.LogMessage("Checking Masterpage Gallery: " + masterpagegallery.Title);
                        Logging.LogMessage("items " + masterpagegallery.Items.Count);
                        foreach (SPListItem pagelayout in masterpagegallery.Items) {
                            Logging.LogMessage("checking layout " + pagelayout.Name);
                            if (featurefilesList.Contains(pagelayout.File.Name.ToLowerInvariant())) {
                                // just uncustomize the pages for the given feature, so that MOSS will point to
                                // the disk version of these (new) files.
                                if (pagelayout.File.CustomizedPageStatus == SPCustomizedPageStatus.Customized) {
                                    // make the page uncustomized
                                    pagelayout.File.RevertContentStream();
                                    Logging.LogMessage("Uncustomized the item: " + pagelayout.File.Name);
                                }
                                else {
                                    Logging.LogMessage("The item was already uncustomized: " + pagelayout.File.Name);
                                }
                            }
                        }
                    }
                }
            }
        }
    }

• Employees login with their AD Account
• Partners, suppliers, customers login through a (Custom) Trusted Identity Provider ( Like facebook,OpenID or custom )

Image you have a CRM Application (like Microsoft Dynamics CRM 4) where you store all the relations (contacts) your company has with customers, partners and suppliers. You can use this information, e.g. the email addresses and a custom field for a password, to create your own Identity Provider and provide access to your extranet/collaboration portal based on the information stored in the CRM application.

In 2007 you would extend your SPWebApplication and configure Forms Based Authentication. You would lose the Client Integration Features of Office (2007), and you needed to configure your Membership Provider in the Web.Config.

In 2010 we can use a Identity provider/Claim Provider. There are some major differences / benefits in comparison to a custom Membership Provider. With an Identity Provider ( custom or not ):

• You can use the Integration Features of the Office (2010) Client
• All users connect on the same url / WebApplication
• You can re-use a Identity Provider on more than one WebApp (it’s now just a Trust thing)
• You have Single Sing On (SSO) for free with other WebApps that Trust the same Identity Provider
• Configuration is done through PowerShell on all servers at once!

This will be a Multi Blog post on “writing your own Trusted Identity provider / Claim Provider for SP2010″.
In order to have a working Trusted Identity provider for SharePoint you will need to do a couple of things:

• Create a Custom Security Token Service with the Windows Identity Framework SDK
• Create a Custom SPClaimProvider ( see part 2 )
• Register your Custom SPClaimProvider ( see part 2 )
• Create a Trust between your Tusted Identity Provider (STS) and SharePoint 2010
• Create or Configure your SP2010 WebApplication to use the Tusted Identity Provider

This post will focus on how to create a Custom Security Token Service with the Windows Identity Framework SDK.

1. Download and install Windows Identity Framework SDK for .Net 4.0 ( and thus VS 2010 )
   SP2010 runs on .Net 3.5 but since this is a Separate IIS WebApplication you use the 4.0
2. Create a new Web Project with VS2010 based on the ASP.Net Security Token Service Web Site template

   

   This will be the Website used by users to actually login to

3. Note the following important classes/methods in the project:
   
   • CustomSecurityTokenService.cs, and especially the method: GetOutputClaimsIdentity
   • Login.aspx, and especially the CodeBehind: Page_Load
   • Web.Config, and especially the appSettings: IssuerName and SigningCertificateName
4. Implement the method GetOutputClaimsIdentity,
   here I have chosen to login with the user’s email address.

   /// <summary>This method returns the claims to be issued in the token.</summary>
   /// <param name="principal">The caller's principal.</param>
   /// <param name="request">The incoming RST, can be
   /// used to obtain addtional information.</param>
   /// <param name="scope">The scope information
   /// corresponding to this request.</param>
   /// <exception cref="ArgumentNullException">If 'principal'
   /// parameter is null.</exception>
   /// <returns>The outgoing claimsIdentity to be included
   /// in the issued token.</returns>
   protected override IClaimsIdentity GetOutputClaimsIdentity(IClaimsPrincipal principal,
                                           RequestSecurityToken request,
                                           Scope scope) {
       if (null == principal) {
           throw new ArgumentNullException("principal");
       }
       // name = the email address of the user
       string name = principal.Identity.Name;
       // create the new identity
       ClaimsIdentity outputIdentity = new ClaimsIdentity();
       // add new claim based on login/email
       outputIdentity.Claims.Add(new Claim(
         System.IdentityModel.Claims.ClaimTypes.Email,
         principal.Identity.Name));
       // return the claim
       return outputIdentity;
   }
   

   If you want to add more claims you can! You could add claims to the output here to facilitate groups of users.
5. Implement the Login button/event in the Login page

   /// <summary>Handle the Page Load</summary>
   /// <param name="sender"></param>
   /// <param name="e"></param>
   protected void Page_Load(object sender, EventArgs e) {
       // Note: Add code to validate user name, password. This code is for illustrative purpose only.
       // Do not use it in production environment.
       if (!string.IsNullOrEmpty(txtUserName.Text)) {
           // Check credentials agains backoffice (Dynamics CRM 4 in this case)
           if (CrmSQLClient.ValidateContactLogin(txtUserName.Text, txtPassword.Text)){
               // Login info is valid, redirect the user.
               if (Request.QueryString["ReturnUrl"] != null) {
                   FormsAuthentication.RedirectFromLoginPage(txtUserName.Text, false);
               }
               else {
                   FormsAuthentication.SetAuthCookie(txtUserName.Text, false);
                   Response.Redirect("default.aspx");
               }
           }
       }
   }
   

6. Change the login page front end
7. Add extra functions like “Forgot my password” or “Register for an account” now or later
8. Deploy your webapplication to IIS.
   You should now be able to login to your custom STS with a browser:
   
9. Create a proper “FederationMetadata.xml”.
   This was a bit hard for me at first. But there is an App for that!
   • Provide the proper values for the WS-Federation Metadata Generator
   • You will need a Certificate to sign the “FederationMetadata.xml” document
   • Copy the new “FederationMetadata.xml” to your published STS Website
10. Test your new STS WebApplication by logging in. You might get an error when you first test this. Use this url to test if your login page works:http://test-server/default.aspx?&wa=wsignin1.0
11. There is one thing left to do when you want to use your Identity Provider: install a certificate on the Web Server, and use that to sign the FederationMetadata.xml and update the Web.Config of your provider to reference this certificate in the IssuerName.

Next post will descibe the SPClaimProvider to create and register.

And be sure to check-out some small “issues” with Claims Based authentication

“SPModule is an example of how we would envision you accomplish various common tasks within Windows PowerShell in a SharePoint 2010 environment.  We hope to position various best practices from these scripts and we hope in the long term to reference these also within technet.  These blog posts serve simply as our first location of sharing them, and this post will be updated once we have the samples hosted within technet.  The scripts themselves are not officially supported.”

The post

The download

Example: “Install SharePoint Bits (including Prereqs)”

Install-SharePoint -SetupExePath “\\servername\SharePoint2010\setup.exe” -PIDKey "PKXTJ-DCM9D-6MM3V-G86P8-MJ8CY"
New-SharePointFarm –DatabaseAccessAccount Get-Credential DOMAIN\username –DatabaseServer "SQL01" –FarmName "TestFarm"

“The SharePoint Site Recycle Bin is a SharePoint Foundation 2010 solution package that when deployed to a Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010 server farm enables administrators to create a snapshot of subscriptions, site collections and Webs as they are deleted through the SharePoint user interface, the SharePoint Administration Tool, the SharePoint 2010 Management Shell, SharePoint 2010 Central Administration, or SharePoint Designer.”

Via http://blogs.technet.com/b/wbaer/archive/2010/08/04/sharepoint-site-recycle-bin-for-sharepoint-2010.aspx

“Access Denied”

How to code and install a SPJobDefinition

Paul Kotlyar found this on the subject:

“Upon detailed investigation of Microsoft.SharePoint.dll  I discovered that SharePoint guys added a new security feature to all objects inheriting from SPPersistedObject in the Microsoft.SharePoint.Administration namespace. This feature explicitly disallows modification of the above stated objects from content web applications, which is where our web part is running. The error message thrown is therefore very misleading. After some more tracing through the code I found a property in SharePoint API which controls this behavior: SPWebService.ContentService.RemoteAdministratorAccessDenied”

Here is how to fix this Access Denied (through powershell):

$snapin="Microsoft.SharePoint.PowerShell"
if (get-pssnapin $snapin -ea "silentlycontinue") {
  write-host -f Green "PSsnapin $snapin is loaded"
}
elseif (get-pssnapin $snapin -registered -ea "silentlycontinue") {
  write-host -f Green "PSsnapin $snapin is registered"
  Add-PSSnapin $snapin
  write-host -f Green "PSsnapin $snapin is loaded"
}
else {
  write-host -f Red "PSSnapin $snapin not found"
}
# get content web service
$contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
# turn off remote administration security
$contentService.RemoteAdministratorAccessDenied = $false
# update the web service
$contentService.Update()

param([string]$folder)
write-host ""
write-host -f Green "Get Solutions from Farm - Stef van Hooijdonk - v1.0"
write-host ""
$snapin="Microsoft.SharePoint.PowerShell"
if (get-pssnapin $snapin -ea "silentlycontinue") {
  write-host -f Green "PSsnapin $snapin is loaded"
}
else {
  if (get-pssnapin $snapin -registered -ea "silentlycontinue") {
    write-host -f Green "PSsnapin $snapin is registered"
    Add-PSSnapin $snapin
    write-host -f Green "PSsnapin $snapin is loaded"
  }
  else {
  write-host -f Red "PSSnapin $snapin not found"
}
}
write-host ""
$folder = Join-Path -Path $folder \ -resolve
if ( Test-Path $folder ) {
  $farm = Get-SPFarm
  foreach($sol in $farm.Solutions){
    $solutionFileName = $folder +$sol.SolutionFile.Name
    $sol.SolutionFile.SaveAs($solutionFileName )
    Write-Host "- saved" $sol.SolutionFile.Name
  }
}
else {
  Write-Host -f Red "ERROR: Folder ""$folder"" does not exist"
}
write-host ""

(22-07-2010) The knowledge base articles are not present yet, so no word on what is updated. Don’t rush to install them just yet

(26-7-2010) The knowledge base articles are present now. And the Claims based authentication issue with Outlook social connector is now fixed!!

ServicePack 1 when it will be released will include these also.

Download links are found here:

http://blogs.technet.com/b/stefan_gossner/archive/2010/07/22/the-first-cumulative-update-for-sharepoint-2010-family-has-been-released.aspx

(Direct links: )

Microsoft SharePoint Foundation 2010:

• KB2028568 – Download

Microsoft SharePoint Server 2010:

• KB983319 – Download (Search 2010 related)
• KB983497 – Download (SP2010 related)
• KB 2182938 – (localized Japanese only) - Download
• KB2281364 – Download (SP2010 related)
• KB2124512 – Download (FilterPack related)
• KB2204024 – Download (WebAnalytics related)

“I am pleased to announce the availability of the first version of the SharePoint 2010 Administration Toolkit. In this toolkit we’ve included a couple of tools that were shipped releases and are now adapted to SharePoint 2010, along with two new tools.”

The toolkit can be downloaded from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en

The toolkit documentation can be found here:

SharePoint Foundation 2010: http://technet.microsoft.com/en-us/library/cc508986.aspx

SharePoint Server 2010: http://technet.microsoft.com/en-us/library/cc508851.aspx  

Read more: http://blogs.msdn.com/b/sharepoint/archive/2010/07/15/announcing-the-release-of-the-sharepoint-2010-administration-toolkit-v1.aspx

When using a SharePoint 2010 Web Application for your portal/mysites with Claims Based authentication the Outlook social connector cannot connect to it!

UPDATE: SP2010 CU1 fixes this!

With Fiddler you will see that Outlook will try to connect to http://portal/_vti_bin/Authentication.asmx

But this returns a response with the word (ModeResult) “Forms”

and that’s why Outlook will show that it cannot connect!

 There is a sort 0f solution for this, create a second webapplication, with a separate url, and connect it to the same User Profile Service application as your portal but configure it with windows authentication. Now users can use this second url in their Outlook Social Connector for Sharepoint.

http://www.microsoft.com/downloads/details.aspx?FamilyID=c148b2df-c7af-46bb-9162-2c9422208504&displaylang=en

This will install 4 VS 2010 Project Templates on which you can base your Custom STS, I used the first one :

Part of a STS is the WS-Federation Metadata document ( . you can create one for your STS with this tool:

http://weblogs.thinktecture.com/cweyer/2009/05/geneva-based-ws-federation-metadata-document-generation-wizard-or-oops-i-did-it-again.html

When you want to trust a STS Token Service within your SP2010 Farm you can use this tool:

http://shojeeb.com/sharepoint/sharepoint-federation-utility-spfedutil-exe/

“Web Applications using Claims authentication require an update”

Just install this hotfix: http://code.msdn.microsoft.com/KB979917 ( the first recorded SP2010 update? )

More info on the issue: http://technet.microsoft.com/en-us/library/ff686815.aspx

Have a look into your Developer Dashboard to see what is going on:

The warning and critical error are:

• 7362 – Warning Publishing Cache
• 7363 – Critical Publishing Cache

Why is this? Because with Claims Based Authentication the Cache account cannot access the Content Databases.

The solution is to provide your SPWebApplication with two settings (Properties):

• portalsuperuseraccount
• portalsuperreaderaccount

If you are lazy, like me, you probably want to automate this into a PowerShell script:

Update 6 juli 2010: This script sets the default managed account as the portalsuperuseraccount and portalsuperreaderaccount. In a production scenario this will work, but it is wiser to use a read only account. Give this account Full Read permission through a Web Application Policy, follow this step-by-step-guide.

write-host ""
write-host -f White "Configure the WebApp property: portalsuperreaderaccount"
write-host ""
write-host -f Green "Stef van Hooijdonk - v1.0"
write-host ""

$snapin="Microsoft.SharePoint.PowerShell"
if (get-pssnapin $snapin -ea "silentlycontinue") {
	write-host -f Green "PSsnapin $snapin is loaded"
}
else {
	if (get-pssnapin $snapin -registered -ea "silentlycontinue") {
		write-host -f Green "PSsnapin $snapin is registered"
		Add-PSSnapin $snapin
		write-host -f Green "PSsnapin $snapin is loaded"
	}
	else {
		write-host -f Red "PSSnapin $snapin not found"
	}
}

write-host -f Green "Getting current Farm"
$farm = Get-SPFarm

write-host -f Green "Getting Default ServiceAccount (Managed)"
$cacheAccount= $farm.DefaultServiceAccount.Name

write-host ""
write-host -f Green "Going to loop Claims Based authentication WebApplications"
write-host ""

Get-SPWebApplication | foreach-object {

	if ($_.UseClaimsAuthentication ) {
	write-host -f white $_.Url " is a Claims Based Authentication WebApp"

	write-host -f yellow " - Setting Property: portalsuperuseraccount $cacheAccount for" $_.Url
	$_.Properties["portalsuperuseraccount"] = "$cacheAccount"

	write-host -f yellow " - Setting Property: portalsuperreaderaccount $cacheAccount for" $_.Url
	$_.Properties["portalsuperreaderaccount"] = "$cacheAccount"

	$_.Update()
	write-host "Saved properties"
	}

}
Write-host ""
Write-host -f red "Going to run IISReset"
Write-host ""
IISreset /noforce
Write-host ""

“Simultaneous editing for collaboration is one of the most hyped features in Office 2010, however it’s only supported over the web in the Excel 2010 web app.  For Word and PowerPoint simultaneous editing, you’ll need to have the full client versions of the Office 2010 products.  This will likely be a disappointment for people who were hoping to collaborate on documents from kiosks anywhere in the world.” (Michael Fettner)

Go over to his blog for the details.

Then you probably have used a FQDN for your portal url.

The fix is quite easy if you have Vista or Windows 7 clients:

http://support.microsoft.com/?id=943280

Short version:

Add a reg key to “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WebClient\Parameters”

with the name: AuthForwardServerList (MULTI_STRING) and add your portal urls as values:

But one thing is not possible, and that is using the Test Projects with your SP2010 projects. Why? because Microsoft did not implement testing with .Net framework 3.5 and below. You can only use the Test projects in VS2010 (and thus in TFS2010) with 4.0 Framework projects. And so you cannot use the Unit test in VS2010 either.

But you can fairly easy use the Nunit 2 framework with VS2010 and TFS2010. Head over to this codeplex project: http://nunit4teambuild.codeplex.com/ and you can now have 3.5 Framework NUnit tests with TFS2010. And your Unittest results even show up in TFS2010 build reports!

So how to get NUnit to test your SP2010 projects? Install SP2010 on your TFS Build Agent! You can then deploy your solutions on the build server, perform unit tests, and then remove your solutions again.

Individual test results:

So what do you need:

- VS 2010 solution with one or more SP2010 projects and at least one NUnit Test project
- TFS Build Agent with SP2010 installed and configured
- A web application for this solution we want to build ( store the web application url in your tfsbuild.proj )
- a deployment script ( powershell off course ) that can be used on you dev server, the Build Agent server (farm) and other farms
- a removal script ( powershell also ) that clears your deployment again
- a tfsbuild.proj that builds, packages and runs the nunit ( see below )
- XSLT to transform NUnit test results to MSTest test results

A powershell script to deploy a solution can be found here
So here is a small overview of my tfsbuild.proj:

- build the solution/projects
- package the projects that are sp2010 projects ( this makes the wsp packages ! )
- run a powershell deployment script
- run nunit against your test project
- run a powershell removal script
- convert the nunit result xml to TFS / MSTest format with xslt ( see codeplex link above )
- upload the nunit transformed test results to tfs with MSTest
- zip the solutions with the scripts
- upload the zip to a location where you can use it on the test environment

Example NUnit code:

        [Test]
        [Category("Features")]
        public void TestFeatures() {
            Assert.IsNotNull(this.projectName, "No valid ProjectName found.");
            Assert.IsNotNull(this.webapp, "No valid Test WebApplication is found.");
            Assert.IsNotNull(this.testsite, "No valid Test Site Collection is found.");

            try {
                //string contenttypes_id = "03ec908f-fc7a-44cf-a8fc-bc3b9d9896de";
                //string trefwoorden_id = "f0455e8e-aa5d-4ae7-8af9-a97947f7e3a0";
                string webparts_id = "f0e1d4d6-2694-479f-8751-9704818f1464";

                SPFeature feature = this.testsite.Features[new Guid(webparts_id)];
                Assert.IsNotNull(feature, "webparts_feature not found active.");

                // check if the webparts are present in the WebPart Gallery

            }
            catch (Exception exc) {
                Assert.Fail(exc.Message);
            }
        }

You can download exmple scripts and proj files here:
Codeplex “release” for this blog

Next in order to create a unique sequenced number I immediatly thought of SQL Server. And found that Ton Stegeman had an equally usefull post on how to create your own SPDatabase object in a SharePoint Farm.

Now I was set to create “the last Document ID Provider” for SP2010 I was ever going to write. Perhaps not but still, it should suffice for a LOT of clients of us!

I wanted to end up with an admin page like this:



This should then result in this document id:



So how to do this?
Step 1
Create a Database with a Table where I can store my generated document id’s

CREATE TABLE [dbo].[scoped_docid](
	[id] [bigint] IDENTITY(1,1) NOT NULL,
	[scopeid] [uniqueidentifier] NOT NULL,
	[objectid] [uniqueidentifier] NOT NULL,
	[scopedocid] [bigint] NULL,
	[scope] [varchar](100) NULL,
	[generateddocid] [varchar](150) NULL,
	[listid] [uniqueidentifier] NULL,
	[webid] [uniqueidentifier] NULL,
	[siteid] [uniqueidentifier] NULL,
	[webapplicationid] [uniqueidentifier] NULL,
	[farmid] [uniqueidentifier] NULL,
	[created] [datetime] NULL,
	CONSTRAINT [PK_scoped_docid] PRIMARY KEY CLUSTERED
(
	[id] ASC
)WITH (PAD_INDEX  = OFF, STATISTICS_NORECOMPUTE  = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS  = ON, ALLOW_PAGE_LOCKS  = ON) ON [PRIMARY]
) ON [PRIMARY]

And a stored procedure to Get/Insert ID’s:

-- =============================================
-- Author:		Stef van Hooijdonk
-- Create date: juni 2010
-- Description:
-- =============================================
CREATE PROCEDURE GetNextScopedDocID
	-- Add the parameters for the stored procedure here

	@scopeid uniqueidentifier  ,
	@scope varchar(100),
	@itemid uniqueidentifier
AS
BEGIN
	-- SET NOCOUNT ON added to prevent extra result sets from
	-- interfering with SELECT statements.
	SET NOCOUNT ON;
	SET TRANSACTION ISOLATION LEVEL READ UNCOMMITTED

	BEGIN TRANSACTION

	declare @result bigint
	declare @scopedindex bigint

	select @scopedindex=COALESCE([scopedocid],-1),@result=[id] from scoped_docid where [objectid] = lower(@itemid)

	if (@scopedindex is null)  begin
		-- coalesce for the first record will have MAX = null, and then we add 1
		select @scopedindex=COALESCE(MAX(scopedocid),0)+1 from scoped_docid where scope = lower(@scope)

		insert into [scoped_docid] (scopeid ,scope,objectid, scopedocid ) values( lower(@scopeid), lower(@scope),LOWER( @itemid), @scopedindex)
		select @result = SCOPE_IDENTITY()
	end
	COMMIT
	select @result as record,@scopedindex as docid
END
GO

There is more to it than this, but you can check out the downloads for all the details.
Step 2
Create an SPDatabase object for this Database, see the Ton Stegeman post!

Step 3
Create a Document ID Provider that uses this SPDatabase and generates Document ID’s based on some settings. What I did was generate the sequenced number in SQL and then format that in a method with the other variables. Generating a YEAR or DAY into a string is fairly easy.

Step 4
Create an Central Admin page to change the settings of our Document ID Provider ( see screenshot ).
You can use the SPFarm.Local.Properties to score your settings Farm Wide:

/// <summary>
/// The default farm wide scope setting for this DocumentProvider
/// </summary>
public ProviderScope Scope {
  get {
    ProviderScope result = ProviderScope.Farm;
    try {
      string setting = Settings.GetFarmSetting("CustomDocumentIDProvider.Scope");
      if (!string.IsNullOrEmpty(setting))
        result = (ProviderScope)Enum.Parse(typeof(ProviderScope), setting);
      }
    }
    catch (Exception exc) {
      LogException(exc);
    }
    return result;
  }
  set {
    Settings.SetFarmSetting("CustomDocumentIDProvider.Scope", value.ToString());
  }
}

The scope:

/// <summary>
/// Scopes for the Document ID Provider
/// </summary>
public enum ProviderScope {
	/// <summary>Farm wide scope</summary>
        Farm=1,
        /// <summary>Webapplication scope</summary>
        Webapplication = 2,
        /// <summary>SPSite/Site collection scope</summary>
        SiteCollection = 3,
        /// <summary>Site/Subweb (SPWeb) scope</summary>
        Site = 4,
        /// <summary>List scope</summary>
        List = 5,
        /// <summary>No scope</summary>
        None = 100
}

Downloads
Download solution
Download sources

How to use the solution

• Install solution
• Navigate to Central Admin. and go to General Application Settings
• Navigate to the Document ID Farm Administration page below the Tam Tam section
• Supply a Database name for your Farm wide document ID provider and press provision
• Supply the settings and formatstring
• Navigate to your site collection and activate the Tam Tam Document ID Provider

Top of your powershell script:

## Start logging
$LogTime = Get-Date -Format yyyy-MM-dd_h-mm
$LogFile = "$env:USERPROFILE\Desktop\Deploy-$LogTime.rtf"
Start-Transcript -Path $LogFile -Force

and put this at the end of your script:

Stop-Transcript
Invoke-Item $LogFile

http://itunes.apple.com/us/app/moshare-a-sharepoint-client/id363305511?mt=8

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=f0c9daf3-4c54-45ed-9bde-7b4d83a8f26f

You navigate to your new SP2010 MySite and want to set it as your default MySite for your office 2010 applications.

But the popup does not come up?

That is because SP2010 ( Office 14 ! ) want’s to activate the ActiveX control “PortalConnect12.PersonalSite”. That is the OFfice 2007 ActiveX control! No wonder it doesn’t work!

The ActiveX control “PortalConnect12.PersonalSite” ( {E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5} )  is present on your system but it registerd itself as the “PortalConnect14.PersonalSite” ActiveX control.

If you run this Registry fix it will start to work again!

Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}]
@="PersonalSite Class"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}\InprocServer32]
@="C:\\Program Files (x86)\\Common Files\\Microsoft Shared\\Portal\\PortalConnectCore.dll"
"ThreadingModel"="Apartment"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}\ProgID]
@="PortalConnect14.PersonalSite.1"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}\Programmable]

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}\TypeLib]
@="{CA973FCA-E9C3-4B24-B864-7218FC1DA7BA}"

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}\VersionIndependentProgID]
@="PortalConnect14.PersonalSite"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite]
@="PersonalSite Class"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CLSID]
@="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite\CurVer]
@="PortalConnect12.PersonalSite.1"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1]
@="PersonalSite Class"

[HKEY_CLASSES_ROOT\PortalConnect12.PersonalSite.1\CLSID]
@="{E7339A62-0E31-4A5E-BA3D-F2FEDFBF8BE5}"

And now when you open your SP2010 MySite: