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

Cherry-pick #24829 to 7.12: [Filebeat] Update Oauth2 flow for m365 defender fileset #24848

Closed
wants to merge 2 commits into from

Conversation

P1llus
Copy link
Member

@P1llus P1llus commented Mar 30, 2021

Cherry-pick of PR #24829 to 7.12 branch. Original message:

What does this PR do?

Microsoft changed the Oauth2 flow from resource to scope based, so the default configuration and documentation needs to reflect that.

Why is it important?

Module won't work without it.

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

P1llus added 2 commits March 30, 2021 15:46
…ith capital letters, and update pytest (elastic#24762)

* updating sophos KV processor to support keys starting with capital letters, adding some missing fields and updating pytest

* Updating changelog

* updating tests to fix errors

* updating tests to fix errors

* removing new tests for now, waiting for kibana module fixes to be applied

* removing new tests for now, waiting for kibana module fixes to be applied

(cherry picked from commit db0d43e)
* updating m365 config and documentation to match new Oauth2 authentication flow

* Update changelog

(cherry picked from commit 55be313)
@elasticmachine
Copy link
Collaborator

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Mar 30, 2021
@P1llus P1llus closed this Mar 30, 2021
@P1llus P1llus deleted the backport_24829_7.12 branch March 30, 2021 14:09
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview

Expand to view the summary

Build stats

  • Build Cause: Pull request #24848 opened

  • Start Time: 2021-03-30T13:50:43.469+0000

  • Duration: 67 min 11 sec

  • Commit: 48bdf09

Test stats 🧪

Test Results
Failed 0
Passed 13028
Skipped 2229
Total 15257

Trends 🧪

Image of Build Times

Image of Tests

💚 Flaky test report

Tests succeeded.

Expand to view the summary

Test stats 🧪

Test Results
Failed 0
Passed 13028
Skipped 2229
Total 15257

@zube zube bot removed the [zube]: Done label Jun 29, 2021
@mergify
Copy link
Contributor

mergify bot commented Jun 29, 2021

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b backport_24829_7.12 upstream/backport_24829_7.12
git merge upstream/7.12
git push upstream backport_24829_7.12

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

Successfully merging this pull request may close these issues.

2 participants