SharePoint 2013

“Value cannot be null. Parameter name: token” for K2 links on SP2013 site in SP2010 compatibility mode

When you¬†migrate Sharepoint and K2 you may run into a problem where all K2 links for your site just give you “Value cannot be null. ¬†Parameter name: token.” I end up having issue after just changing site collection compatibility range (for testing purposes, here is how to do it) and then creating new site within “Value cannot be null. Parameter name: token” for K2 links on SP2013 site in SP2010 compatibility mode

Switching SP2010 from Classic Mode to Claims Mode Authentication

SharePoint Server 2013 uses claims-based authentication as its default authentication model, and it is required to enable its advanced functionality. Using claims-based authentication has the following advantages over using Windows classic-mode authentication: External SharePoint apps support. App authentication and server-to-server authentication rely on claims-based authentication. With Windows classic-mode authentication you are unable to use external Switching SP2010 from Classic Mode to Claims Mode Authentication

How to check whether the UPA properties are populated correctly for specific user

Certain SharePoint 2013 features as well as K2 for SharePoint need to have User Profile Application (UPA) working and its database populated with correct data. Sometimes it is difficult to confirm whether or not UPA is correctly configured as SharePoint UI does not show you all the properties for the users. Moreover, even if UPA How to check whether the UPA properties are populated correctly for specific user