Unable to get token for sharepoint
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- python
- Domain
- api, authentication
Research direction
Start by reviewing the daemon's client-credential scope handling and the Azure app registration permissions described in the issue. Compare the /.default token request with the SharePoint API response; done means establishing whether SharePoint accepts this app-only flow or documenting the required authentication path.
Written by the indexing model from the issue text.
Description
Hi everyone
I'm trying to use this library to authenticate with microsoft using a python deamon. I need to use it to access sharepoint lists so the scope I'm using is https://mytenant.sharepoint.com/AllSites.Read. But I'm always faced with the following error:
AADSTS1002012: The provided value for scope https://mytenant.sharepoint.com/AllSites.FullControl is not valid. Client credential flows must have a scope value with /.default
When trying to use the scope https://mytenant.sharepoint.com/.default, it returns an access token but the sharepoint api returns Unsupported app only token.. I've already given the permissions AllSites.FullControl, Sites.FullControl.All, Sites.Search.All and many others related to sharepoint on the apps registration portal of Azure AD.
Is it not possible to query sharepoint with a "deamon". Is it not possible without redirecting the user to a browser login?
Thanks in advance
- Dominant language
- PowerShell
- Stars
- 62
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure-Samples/ms-identity-python-daemon
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
Azure-Samples/ms-identity-python-daemon#30 · 1 reaction ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
Azure-Samples/ms-identity-python-daemon#23 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
All issues in Azure-Samples/ms-identity-python-daemon
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
phoenixframework/phoenix_live_view#4469 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area/agents
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Blob endpoint returns 406 for an empty Accept headerPossibly taken @am9zZWY claimed this today. OpenIssue Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pulp/pulp_container#2544 ·
Maintainers usually reply within 1 day