Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sharepoint Online: sync not working on new tenant due to Azure ACS retirement #3023

Open
jlnmrtn opened this issue Dec 9, 2024 · 1 comment

Comments

@jlnmrtn
Copy link

jlnmrtn commented Dec 9, 2024

Bug Description

Sync not working for the sharepoint online connector for newly created (after 01/11/24) MS365 tenants, because ACS got retired for new tenant since November 1st 2024 as per: https://learn.microsoft.com/en-us/sharepoint/dev/sp-add-ins/retirement-announcement-for-azure-acs

To Reproduce

Steps to reproduce the behavior:

  1. Create a new MS365 tenant
  2. Create a sharepoint site
  3. Follow the documention https://www.elastic.co/guide/en/elasticsearch/reference/current/es-connectors-sharepoint-online.html#es-connectors-sharepoi[…]-oauth-app-permissions
  4. You will hit the first error, indeed unable to turn ACS on again using the powershell cmdlet Image
  5. Second issue you will get is by running the connector: Image
aiohttp.client_exceptions.ClientResponseError: 401, message='Unauthorized', url="https://ttj57.sharepoint.com/sites/scoobypoint/_api/web/lists/GetByTitle('Site%20Pages')/items?$select=*,EncodedAbsUrl"

Expected behavior

No 401 authorization error , sync happening correctly

Environment

  • Elasticsearch 8.16.1
  • Connector 8.16.1 , managed and selfmanaged

Additional context

Permissions issue can be reproduce by doing the following call (an access token need to be obtained first):

  • Request:
curl --location --globoff 'https://ttj57.sharepoint.com/_api/web/lists/GetByTitle('\''{list_title}'\'')' \
--header 'Authorization: Bearer 1NiIsIng1dC....' \
--header 'Accept: application/json;odata=verbose'
  • Answer:
{
    "error": "invalid_request",
    "error_description": "Token type is not allowed."
}

This error is due to ACS disabled

@seanstory
Copy link
Member

@danajuratoni @erikcurrin-elastic I'm leaving this as "high" for now, since it does seem like a significant regression. But also the most urgent deadline for fixing this (to prevent breakage for existing users) is April 2026, so there's some grey area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants