We have a few applications that currently use managed code CSOM against SP2010 - think of SharePoint as simply a large file store. The UI is not used at all and all the functionality for the remote app is in the remote app - SP is only a file store. All of this was developed with CSOM and authentication was handled via Kerberos delegation (browser->Remove App IIS->SP2010) under the end users credentials. In reality, the app reads files from about 50 sites - and that changes constantly as the data grows so we don't have too many items in a list or too large of a database.

We want to do the exact same thing but move the file store to SP2013 (on-prem) but SP2013 is only setup to use claims - not kerberos. Is there a way to get the CSOM code authenticated properly - everything we try throws 401's right now? Does this require a provider hosted app setup?

Anything to get me pointed in the right direction will be helpful!


1 Answer 1


To use apps in an on-prem SP2013 farm, you need to connect the farm to Azure ACS or run server-to-server.


  • let me change this a bit - I don't want to use apps at all. I just want to retrieve some data from SharePoint (that uses Claims) and I don't want to tell SharePoint anything about it as far as Apps go. Since this works via only a Single hop, can't I setup some type of server 2 server trust so it still works? Jan 15, 2015 at 16:47
  • If your web app is configured to use Integrated Windows Auth, then you can set the Credentials property on the ClientContext. If you are using a Trusted Identity Provider (federated), then your code will need to perform the auth. This SP2010 code should still apply: msdn.microsoft.com/en-us/library/office/… Jan 15, 2015 at 20:32

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.