@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?
username, password and the url like https://company.com/sites/test.
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.
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?
for ADFS, you need not only username and password but relyingParty and adfsUrl
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
- On-Demand
- Add-in Only
- SAML but with user app-password - https://docs.microsoft.com/en-us/azure/active-directory/user-help/multi-factor-authentication-end-user-app-passwords
[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."}}}
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);
});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.
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!>
https://contoso.sharepoint.com/sites/a-site <- valid, https://contoso.sharepoint.com/sites/a-site/folder-path <- invalidThe 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.
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');
}
});
This is my code:
I need users of an SPFX webpart to be able to make permission changes on a site collection on SPO. Elevated permissions etc.
a way to enable SPFX client side webparts to run with elevated permissions?
@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.
Is it possible to get user photos from the graph without having my SPFX web part needing to be authorised by admin? I guess I need clarification on this:
By default, the service principal has no explicit permissions granted to access the Microsoft Graph. However, if you request an access token for the Microsoft Graph, you get a token with the user_impersonation permission scope that can be used for reading information about the users (that is, User.Read.All).
Source: https://docs.microsoft.com/en-us/sharepoint/dev/spfx/use-msgraph#available-permission-scopes
The problem I have is that I'm working with an NHS (Health Service) client in the UK - they use the government's Hybrid 365 offering, which melds NHS Mail with Office 365. The central administration / azure stuff is all handled by Accenture, so I don't have easy access to any of that. Its possible to apply via their desk to have something approved but its such a pain and if there's a way to avoid it I'm all ears...
All I want are profile photos. I am finding /_layouts/15/userphoto.aspx?size=L&username=workemailhere a bit unreliable. https://outlook.office365.com/owa/service.svc/s/GetPersonaPhoto?email=workemailhere works - but I'm finding that if users haven't opened Outlook OWA in addition to SharePoint - the images don't necessarily load. Same thing with Delve.
Any help most appreciated!