const CertStore = require('@microsoft/gulp-core-build-serve/lib/CertificateStore');
const RestProxy = require('sp-rest-proxy');
const CertificateStore = CertStore.CertificateStore || CertificateStore.default;
const settings = {
configPath: './config/private.json',
port: 4323,
protocol: 'https',
ssl: {
cert: CertificateStore.instance.certificateData,
key: CertificateStore.instance.keyData
}
};
const restProxy = new RestProxy(settings);
restProxy.serve();
hi
New here, so excuse if I tackle asking this question the wrong way
I have a node js app running on a server that connects to SharePoint using adfs (node-sp-auth)
Works like a charm
Porting this app to a new env, the admins of that env tell me to 'include the (url of the) identity provider to be used for authentication' ....
Right. ??
Don't know if my question makes sense, but all help is greatly appreciated
When I go to a SP site via the browser I get a (logon) screen, which asks me to choose the place (identity provider ?) where my credentials are kept.
After choosing that I can give my credentials
My node app has no knowledge of this 'choosing an identity provider' so the authentication fails ? because the receiving end does not know where to validate ?
Hence the admins ask me to 'include the identity provider in my call
That's what I make of it anyway
getlistitemchangessincetoken API endpoint (see more: https://docs.microsoft.com/en-us/sharepoint/dev/sp-add-ins/synchronize-sharepoint-items-using-the-rest-service) the actual changes can be recived.
nodejs is an "environment" to run javascript on a server (i.e. in your operation system process), like .NET but for javascript
when you run react app, it runs inside your browser, which is different from nodejs
node-sp-auth uses some things from the underlying operation system, thus making it impossible to run in-browser (in react app for example)
tbh that's not a trivial question, it depends on type of authentication used by your SharePoint instance you're trying to reach out
one option would be implementing the same type of authentication in your app, then enabling cors in SharePoint 2013 to be able to send cors request from one domain (your app) to SharePoint
another option use server-side code with any kind of authentication (username and password) and perform all kind of operation from server
the last option is provider-hosted app
you can try to post your question on a forum https://sharepoint.stackexchange.com or https://techcommunity.microsoft.com/t5/SharePoint/bd-p/SharePoint_General
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