Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    klaydze
    @klaydze
    Hello, hope everybody doing great. Maybe this is a simple error for someone but I'm not really sure why I'm getting a Invalid parameter error every time I execute the below code. Can someone help me pin point what I missed here?
    const url = 'https://company.com/sites/test/Lists/Cleanup';
    spauth.getAuth(url, {
        username: `domain\\my_user_name`,
        password: `my_password`
    }).then((value) => {
        console.log('Connected to Sharepoint');
        console.log(value);
    }, (err) => {
        console.log(err);
    });
    Andrew Koltyakov
    @koltyakov

    @klaydze your site url leads to a list but not SPWeb. Can you try https://company.com/sites/test instead of https://company.com/sites/test/Lists/Cleanup.

    Are you also sure that NTLM auth provider is used?

    klaydze
    @klaydze
    @koltyakov I have updated my url and the error is the same. Forgive my noobness as this is my first time to work with NodeJS and SharePoint, but how do I now if it's NTLM auth provider? One of my teammate just share me a username, password and the url like https://company.com/sites/test.
    Andrew Koltyakov
    @koltyakov
    When you login manually, are you entering login password in a basic popup dialog, or you're navigated to a login page?
    Is in On-Prem of SharePoint Online?
    Generally you just know what auth strategy to use based on what is configured. It can be different options (https://github.com/s-KaiNet/node-sp-auth/wiki).
    klaydze
    @klaydze
    @koltyakov Ah yes, when I visit https://company.com/sites/test then it will redirect me to a login page where I can input the username and password provided. And also, when I'm successfully logged in, when I hit https://company.com/sites/test/_api/lists I will return some data in xml. BTW, this is On-Prem also.
    Andrew Koltyakov
    @koltyakov

    for troubleshooting can suggest this https://github.com/koltyakov/node-sp-auth-troubleshoot
    you could try different options quickly and see if any works

    for on-prem could be:

    • FBA
    • ADFS

    The page there you were redirected, what does it contain in the URL? E.g. is there /adfs/ls in the url?

    It's likely ADFS, so this article https://github.com/s-KaiNet/node-sp-auth/wiki/ADFS-user-credentials-authentication
    for ADFS, you need not only username and password but relyingParty and adfsUrl
    Andrew Koltyakov
    @koltyakov
    as a hint - adfsUrl is where you're redirected when logging in, relyingParty can be found as a parameter in the url
    klaydze
    @klaydze
    @koltyakov Ohh yeah! you are right when I enter the username and click the Next button my URL contains /adfs/ls?client-request-id=42.... and that's the only time that I can enter my password.
    Andrew Koltyakov
    @koltyakov
    wait a sec, entering username then next? adfs page is usually contain both username/pass on the same form and redirected to right away
    the next step is a common way for AAD when before resolving a username it's not known how to authenticate
    are you sure it's not SPO?
    anyways node-sp-auth-troubleshoot and trying different options is for the rescue
    Ralf Brennscheidt
    @RalfBrennscheidt
    Is SP-Online supported with MFA ? Didn't found anything in the wiki/docs related to MFA
    Andrew Koltyakov
    @koltyakov
    With MFA, these node-sp-auth strategies can be used:
    Ralf Brennscheidt
    @RalfBrennscheidt
    :thumbsup:
    Craig The BabelFish
    @Babelfish112_twitter
    Hi all, newbie here. I'm trying to use spsave for NodeJS but running into some issues. I've tested spauth on its own and it's working (response includes a cookie), but running spsave with my URL is giving me GotError: Unexpected token < in JSON at position 2 in <full URL here>. This is with SharePoint online in our domain. I've tried every form of the URL I can think of (https://<company>.sharepoint.com/sites/<team folder>, https://<company>.sharepoint.com/:f:/s/<team folder> etc) and still no luck
    Would greatly appreciate any pointers! Thanks
    Craig The BabelFish
    @Babelfish112_twitter
    Using https://<company>.sharepoint.com/sites/<team folder>, I'm getting:
    [18:17:52] spsave: Error occured:
    [18:17:52] spsave: Response code 403 (Forbidden)
    [18:17:52] spsave: {"error":{"code":"-2147024891, System.UnauthorizedAccessException","message":{"lang":"en-US","value":"Access denied. You do not have permission to perform this action or access this resource."}}}
    But I am set to "Owner" for group membership in SharePoint
    My NodeJS code:
    var coreOptions = {
    siteUrl: 'https://<company>.sharepoint.com/sites/<team folder>/',
    };
    var creds = {
    username: '<username>',
    password: '<password>',
    // online: true
    };
    var fileOptions = {
        folder: 'Test',
        fileName: 'file.txt',
        fileContent: 'hello world'
    };
    spsave(coreOptions, creds, fileOptions)
    .then(function(){
        console.log('saved');
    })
    .catch(function(err){
        console.log(err);
    });
    Andrew Koltyakov
    @koltyakov

    Hi @Babelfish112_twitter,

    No permissions usually means "no permissions".

    In SPO and when you know you have permissions, e.g. is admin, it's also can be a result of disabled custom scripts.
    This is a good article on the topic how to enable custom scripts: https://www.koskila.net/how-to-enable-custom-scripts-for-a-sharepoint-online-site-collection/
    Or using M365Cli: spo site classic set --url https://<company>.sharepoint.com/sites/<site> --noScriptSite false

    Another thing which might be is than you're providing siteUrl with a wrong path not to the SPWeb but folder.

    Craig The BabelFish
    @Babelfish112_twitter
    Hi @koltyakov, thank you for the suggestions. I will check with the SP admin if custom scripts are disabled

    As for the URL, I am a bit confused what I am meant to use.

    In SP, I am browsing the folder and the URL in the browser is https://<company>.sharepoint.com/sites/<team folder>/Shared%20Documents/Forms/AllItems.aspx?newTargetListUrl=<LONG HTML-formatted STRING!>

    If I put the siteUrl as 'https://<company>.sharepoint.com/' with folder 'sites/<team folder>/Test' spsave apparently works, and says file.txt successfully uploaded to that URL. But the file is not actually there
    Andrew Koltyakov
    @koltyakov
    An example of site url is https://contoso.sharepoint.com/sites/a-site <- valid, https://contoso.sharepoint.com/sites/a-site/folder-path <- invalid
    The API calls are constructed as ${siteUrl}/_api/... and won't be correct with a folder placed in there. The folder path should be in "folder" prop in fileOptions.
    Craig The BabelFish
    @Babelfish112_twitter
    Thanks again. With that form of the URL and folder set, I'm getting the 403 forbidden. Looks like it might be the disabled custom scripts
    Craig The BabelFish
    @Babelfish112_twitter
    So it turns out that custom scripts was already enabled, and my siteUrl was correct. But for the folder I had to prefix it with Shared%20Documents/<folder name>, since my new folder is under Documents. Glad to have this resolved after a day of attempts, and thanks again @koltyakov
    klaydze
    @klaydze
    Can you suggest what is the best way to handle a retry strategy if ever the spr.requestDigest or spr.post have problem connecting to SP?
        await spr.requestDigest(baseUrl)
            .then(async (digest) => {
                const header = {
                    'X-RequestDigest': digest,
                    'Accept': 'application/json;odata=verbose',
                    'Content-Type': 'application/json;odata=verbose',
                };
    
                return spr.post(`${baseUrl}${itemsPath}`, {
                    json: true,
                    body: item,
                    headers: header
                });
            })
            .then(res => {
                console.log('Successfully inserted in Sharepoint!');
                spItems.push(element);
            }, err => {
                if (err.statusCode === 404) {
                    console.log('Not found!');
                } else {
                    console.log('error');
                }
            });
    Marten Meijboom
    @MagicMarten
    image.png
    image.png
    Hi, I am creating an excel file using excel4node, which returns a node buffer. I then want to upload this to SharePoint. When I do this the Excel file in SharePoint is corrupted.
    This is my code:
    Oh... uploaded the images first
    I was wondering if you have any experience with such a situation, and, if there is a way for me to see if this is a mistake with my use of excel4node or spsave
    image.png
    Marten Meijboom
    @MagicMarten
    Managed to figure out that the created Excel file is not corrupt before uploading to Sharepoint
    Marten Meijboom
    @MagicMarten
    image.png
    This is my new code. Both test excel files created locally are fine
    12annumishra17
    @12annumishra17
    Hey Team
    Need help in Onpremise sharepoint
    12annumishra17
    @12annumishra17
    I am trying to make a rest CALL which says 402 unauthorized
    While from browser it gives out the response but from postman when I try it says unauthorized
    cardinalpipkin
    @cardinalpipkin
    Hi - I need to know if this still works: https://github.com/s-KaiNet/node-sp-auth
    I need users of an SPFX webpart to be able to make permission changes on a site collection on SPO. Elevated permissions etc.
    cardinalpipkin
    @cardinalpipkin
    @koltyakov - Is https://github.com/koltyakov/sp-rest-proxy
    a way to enable SPFX client side webparts to run with elevated permissions?
    Andrew Koltyakov
    @koltyakov
    Proxy is for local workbench, during dev time. Not for elevating permissions.
    With node-sp-auth you can authenticate a backend in Azure to call SP APIs on demand of a service account.
    The service should be protected with AAD.
    cardinalpipkin
    @cardinalpipkin
    @koltyakov - thanks. Not for me then. Do you know if Graph API can be used to impersonate/elevate permissions for SPFX webpart? I understand that this functionality will be implemented into a future version of SPFX. Do you know if it already has?
    Andrew Koltyakov
    @koltyakov
    There is no client-side way for impersonation. Only:
    • Call a web service which authenticates user, decides if a user allowed for an action, then calls another service with service acc context
    • Indirect delayed impersonation: like create an item which calls a workflow/flow
    cardinalpipkin
    @cardinalpipkin
    @koltyakov - "Indirect delayed impersonation: like create an item which calls a workflow/flow" can you give me an example of this?
    Andrew Koltyakov
    @koltyakov

    @cardinalpipkin this "create an item which calls a workflow/flow" is actually an example =)

    Well ok, let me elaborate:

    • There is a list Customers which is read-only for a user
    • As an elevation scenario a user should update Customer's status
    • There is another Actions list where a user can add items into it
    • In an app, for changing a status a user creates a "signal" item in Actions
    • On item creation in Actions list, a Flow/WF/Webhook* is triggered
    • What is triggered checks is an author has "rights" to update a status and if so, updates Customer's item using permissions elevation step/etc.
    cardinalpipkin
    @cardinalpipkin
    @koltyakov - Thanks. I'm using MS Flow to break inheritance and clear all permissions with an uploaded file, then JavaScript attempts to rename the FileLeafRef of the doc. Problem is....timing. MS Flows are slow to start so the triggering user doesn't have permission on the file and the JavaScript cannot rename the file. I have to clear permissions on each file because it's a shared lib. The limitations of client side coding with SharePoint!!!!