SharePoint 2013 Authentication


Hello everyone,

As some have seen, when you create a new web application in SharePoint 2013, the only authentication mode available via the UI is the “Claim-based authentication.”

The reason is that Office Web Apps can work only with this model. However, it is possible to create web applications using the NTLM or Kerberos via Powershell.

To do so, you must use a command line such



New-SPWebApplication -Name "Contoso Internet Site" -ApplicationPool "ContosoAppPool" -AuthenticationMethod "Kerberos" -ApplicationPoolAccount (Get-SPManagedAccount "CONTOSO\jdoe") -Port 80 -URL "https://www.contoso.com"

More information on this subject here: http://technet.microsoft.com/en-us/library/gg276326.aspx

For application migrations, it is also possible to migrate from one mode “classic” mode “Claim-Based”, the procedure can be found here: http://technet.microsoft.com/en-us/library/gg251985.aspx

Hope this help !

Christopher.

Advertisements

Custom development not found in production


Hello everyone,

Today I want to talk to the new SharePoint developers who started with Visual Studio 2010.

Browsing the forums, I often come to see messages such as: “I ​​do not understand, my development work properly on my development environment, but after my wsp deployed in production, I do not see my new webpart / my new controls / etc .. ‘

Visual Studio 2010 has integrated functionality that although it can be useful for people who are new, I abhor, namely the automatic activation of features!

If you check your project properties, you can find the property “Active Deployment Configuration”

When this property is set to “Default” (as it is by default), when you deploy via Visual Studio, it automatically activates the features existing in your project on your development site!

If it is convenient not to have to go through the manual activation, it has a double disadvantage for me:

1) Developer who is not familiar with the deployment mechanism finds himself lost when deploying his package on another environment because he doesn’t know and / or do not think about the features activation!

2) For delicate developments such as content types, if you reactivate the feature while you have some content, you may have a nice error message saying that the content type ID is already present.

To avoid automatic activation by Visual Studio, you can put this property in “No Activation”

Think about it.

Christopher.

Display ribbon when multiple ListViewWebPart on the page


Hello everyone,

Some time ago I wrote about a script to display the ribbon on the pages where several ListViewWebPart were present (see here).

The idea of ​​this script was to simulate a click on a ListViewWebPart to view the ribbon. However, it seems JavaScript function “WPClick” used in SharePoint 2010 does not work correctly on 2013!

To simulate clicking on the Web, we must now use the following script.



ExecuteOrDelayUntilScriptLoaded(ShowContextRibbonSections, "sp.ribbon.js");

function ShowContextRibbonSections(){

    var initInfo = {

          editable: true,isEditMode: false,allowWebPartAdder: false

    };

    SP.Ribbon.WebPartComponent.registerWithPageManager(initInfo);

    var wpcomp = SP.Ribbon.WebPartComponent.get_instance();

    if(wpcomp){

         var zc = document.getElementById("MSOZoneCell_WebPartWPQ2");

         wpcomp.selectWebPart(zc, true);

    }

}

This new script was found by a member of the msdn forums: http://social.msdn.microsoft.com/Forums/en-US/sharepointdevelopment/thread/c4c988e2-805c-49a4-a5bf-5097dedcef58

Thank Peter Azure for this tip!

Christopher