Skip to content

Latest commit

 

History

History
69 lines (54 loc) · 3.4 KB

README.md

File metadata and controls

69 lines (54 loc) · 3.4 KB
Raw

SharePoint 2013 apps with node.js

This is sort of a proof-of-concept for creating node.js apps with SharePoint 2013, using web sockets and everything. The strategy for SharePoint authentication is mostly taken from here, but it has been modified a bit. Mostly I stripped away stuff that I did not need for my own understanding. https://github.com/QuePort/passport-sharepoint

The basic idea is that you deploy an appmanifest so SharePoint pointing to a website running this node.js webapplication. SharePoint will go fetch encrypted refresh-tokens from ACS which the client will then post to this web app. This app, knowing the app secret, will decode the encrypted token and then go to ACS to get the auth token. Then, it can go to SharePoint to get user data etc. And it does a lot of stuff to connect the authenticated https sessions to web sockets. I realize there is a lot of documentation to do. But it's a proof of concept and it sort of works.

TODO

todo... a lot of stuff Stub out the authorization server and decouple all the things

Creating certs for https on localhost

I've checked in some dummy certs, but in case they won't work or something, here's how I created them.

openssl genrsa -out privatekey.pem 2048 
openssl req -new -key privatekey.pem -out certrequest.csr 
openssl x509 -req -in certrequest.csr -signkey privatekey.pem -out certificate.pem

Keys

I can't put the secrets in here, so I have not uploaded any real keys. You should make your own cookieSecret and get your own clientID and clientSecretfrom SharePoint when you deploy the app. You can put them in the keys file, like shown below, or if you use nodejitsu to run your app, like I do, you can use environment variables.

a keys.js file should contain secret keys for app and cookie-signing

    var clientID = "17b74aca-d3b1-39a5-b11a-892043384b3a";
    var clientSecret = "Lbac16P1mX+amQjmfP2psKMahsfnTbsJKzv19jLi4b0=";
    var cookieSecret = "thisisfreakinghardtoguess";
    module.exports = {"clientID" : clientID,
                      "clientSecret" : clientSecret,
                      "cookieSecret" : cookieSecret};

when using nodejitsu, like I do, you can run

    jitsu env set clientID "17b74aca-d3b1-39a5-b11a-892043384b3a"
    jitsu env set clientSecret "Lbac16P1mX+amQjmfP2psKMahsfnTbsJKzv19jLi4b0=";
    jitsu env set cookieSecret "thisisfreakinghardtoguess";

OAuth 2.0 dance

SharePoint Client Object Model

To allow for cross-domain calls (when the client, as in the browser of the user accessing the site, requests data directly from SharePoint) we use the SP.Request.Executor. This creates an iframe in the page that are used to make calls to SharePoint. I haven't tested it, but I think it works once we add the following little bit of code into the app. This should open up to cross-domain calls from scripts hosted on our provider hosted app site.

#TODO - update the app-docs

<AppPrincipal>
    <Internal AllowedRemoteHostUrl="https://localhost:1337"/>
</AppPrincipal>

According to http://msdn.microsoft.com/en-us/library/jj163816.aspx

This gives us two ways for getting data from SharePoint:

  • Using REST calls from the app server
    • This uses app permissions
  • Using Client Object model from the clients
    • I think this is using the users permission on the site, but it might acutally be altered somehow in combination with the app rights