beyond-sharepoint/spo-remote-auth

This module provides a generic remote authentication implementation against SharePoint online.

spo-remote-auth's Issues

Auto-prefix SPO url with https://

If https:// is left out of the url, a STS token error is displayed.

Have the library ensure that https:// is present as SPO is all SSL

fs.readFileSync is not a function

Hi @Oceanswave, spo-remote-auth seems to be perfect for the project I'm working on but I'm hitting the error fs.readFileSync is not a function. I've tried to develop a work around but have been unsuccessful thus far. I've seen a number of examples of other libraries having issues with this same node file system method.

It's an Ionic (Angular) project using webpack. Forgive me if I'm missing a silly/obvious mistake.

Any thoughts?

Auto-Renew currentContext()

Currently, ensureCurrentContext() must be executed in long-running processes prior to each each request to ensure that the X-RequestDigest is current.

It would be great if the library automatically did this per request, and renewed the context automatically.

This would change the interface a bit, as there would need to be a shim in front of each request.js method (similar to ntlm-remote-auth) to perform this step.

Replace Xml2Json with another library.

Folks are having trouble installing spo-remote-auth because of the node-xml2json dependency which requires node-expat to be installed.

different authentication server?

I can't get any access method to SharePoint to work with my login credentials, including SPO.

I suspect the problem is that we have a custom login portal - when I browse to login.microsoft.com, I'm sent to adsf.ourdomain.com to enter my login and password.

Does/should spo-remote-auth (and therefore spo-shell) handle this correctly? I'm stumped.