I would suggest trying client id and client secret (aka add-in auth)
use this wiki page to find out how to configure it https://github.com/s-KaiNet/node-sp-auth/wiki/SharePoint-Online-addin-only-authentication
use this wiki page to find out how to configure it https://github.com/s-KaiNet/node-sp-auth/wiki/SharePoint-Online-addin-only-authentication
but maybe I have a problem with sharepoint, what is site, what is a folder. I am very new to sharepoint :D
yeah it works. I had a problem with understanding what is a folder and what is a site :D sorry for bothering you
If it's SharePoint Online, custom script can be disabled by default. In case of custom scripts even being a site collection admin you are blocked in uploading a single JS/CSS, etc. Check this for details https://www.koskila.net/how-to-enable-custom-scripts-for-a-sharepoint-online-site-collection/
but i writing an extension for vscode, which make it possible to upload folders to sharepoint. Therefor they have to follow some folder structure to get there stuff to the right place. But If they have a bad folder structure and try to upload their stuff to the wrong, not existing, place, I can't give them response
Have you seen spgo extension? https://marketplace.visualstudio.com/items?itemName=SiteGo.spgo probably you don't event need a custom one
OK I don't know if the solution is a benefit for spsave, because I am a junior developer and new to sharepoint. But what I have:
export async function getLibraryItems(libraryUrl: string, con: IConnection): Promise<string[]> {
let apiUrl = libraryUrl.endsWith("/") ? libraryUrl + "_api/web/lists" : libraryUrl + "/_api/web/lists";
let reqR = await sharepointGET(apiUrl, con);
let arr: any[] = reqR.d.results;
let result: string[] = [];
for (let i: number = 0, l: number = arr.length; i < l; i++) {
result.push(arr[i].Title);
}
return result;
}
In my case (I don't know if it is for every case), uploading is always to a library. So I will use the method above to check what folders? I have in the library and save the result in a static variable (don't call it every time) | staticVar[libraryUrl] = result;
if the root folder is not in the variable I will do a doublecheck (maybe someone did an update) and in case the folder is not in it I throw an error.
And sry for my bad writing :-)
Hi there, I am trying to use node-sp-auth with a react app but I am getting
Error: process.binding is not supported error so I am guessing that package doesn't support process binding with browser. Does anyone know any modern client side library that does the authentication with sharepoint 2013?
@ahmadali_saeed_twitter you can't use node-sp-auth in browser. it's a library designed for Node.js. Check this possibility out: https://www.linkedin.com/pulse/getting-started-react-local-development-sharepoint-andrew-koltyakov/ - the proxy targets for the anvironment and node-sp-auth is under the hood to deal with auth
@koltyakov that's a very good idea to create a server perform and the operations through that but there is no other way to perform auth with sharepoint 2013 on Client? I don't mind writing my own wrapper package but I couldn't find my information about how auth works in sharepoint on premises.
So my next question is do I now just call local host 8080 in one visual studio code browser and have a separate react one that fetches local host 8080?
It's not about the browser. What is used to serve React app locally, Webpack Dev Server? If a local web server supports API proxying it should be provided with a URL for the API endpoint (it's described in details in the mentined article). If a local web server doesn't support API proxying, in the client side application the requests should be routed correspondenly (when localhost, use proxy's address but not the same as the app is hosted on).
It's better asking here https://gitter.im/OfficeDev/PnP-JS-Core yet in this lobby many knows PnPjs as well.
I'm trying connect to SharePoint 2013 from Node
import { sp } from "@pnp/sp";
import { SPFetchClient } from "@pnp/nodejs";
sp.setup({
sp: {
fetchClientFactory: () => {
return new SPFetchClient("{site url}", "{client id}", "{client secret}");
},
},
});
sp.web.select("Title", "Description").get().then(w => {
console.log(JSON.stringify(w, null, 4));
});But i've got 401 Unauthorized
Please help me understand the reason of the error.
Response headers:
Request headers:
Answered you in another tread as well, SPFetchClient's AddIn-Only permissions works for SPO, not On-Prem. For onprem pnp-auth is a auth library of choice https://github.com/SharePoint-NodeJS/pnp-auth#manual-bootstrap
@himyulian, I recalled you asked related question in node-sp-auth-config repository. This toolchain is for Node.js and can not be bundled as a frontend code and what more, can not work on frontend client-side in most of the situations and for 100% for OnPrem. Can you you describe your use case that you try implementing. I have a feeling that you try developing a webpart/client-side app (using Vue) locally in its dev web server and consuming SharePoint API during development. But after an app is built it will be deployed to SharePoint page? Am I right in this assumption? If it's true, another approach should work for you - https://github.com/koltyakov/sp-rest-proxy - and some details on React example which should not be complicated to reuse in Vue toolchain as well.
I have a problem with spsave. I can't transpile it. (tsc --version Version 3.3.3333, "spsave": "^3.1.5"). Transpile error:
node_modules/@types/request-promise/index.d.ts:26:49 - error TS2694: Namespace 'request' has no exported member 'Response'.
Is there a trick?
node_modules/@types/request-promise/index.d.ts:26:49 - error TS2694: Namespace 'request' has no exported member 'Response'.
Is there a trick?
That is my typescript code:
import { spsave } from "spsave";
console.log(spsave.name);
//Just to test it
import { spsave } from "spsave";
console.log(spsave.name);
//Just to test it
oh moment
yeah works, but I don't get that property suggested...
@koltyakov thanks for help
AddIn Only permissions can be configured (https://github.com/s-kainet/node-sp-auth/wiki/SharePoint-on-premise-addin-only-authentication) or the web app extended to another auth type support, NTLM.
Hi @s-KaiNet!