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.

Sign up for GitHub

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

Jump to bottom

[8.16](backport #42212) [filebeat][streaming] - Added OAuth2 support with auto token refresh for websockets #42242

Merged
merged 2 commits into from
Jan 7, 2025
Merged

[8.16](backport #42212) [filebeat][streaming] - Added OAuth2 support with auto token refresh for websockets #42242

merged 2 commits into from
Jan 7, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 7, 2025

Type of change

  • Enhancement
  • Docs

Proposed commit message

Added OAuth2 support with auto token refresh for websockets. A manual token refresh logic had to be implemented since the OAuth2 client and the websocket client are separate entities and cannot be clubbed together.

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.

Disruptive User Impact

NONE

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Use cases

Screenshots

Logs

This is an automatic backport of pull request #42212 done by [Mergify](https://mergify.com).

@ShourieG @mergify
[filebeat][streaming] - Added OAuth2 support with auto token refresh …
7801c7d 
…for websockets (#42212)

* Added OAuth2 support with auto token refresh for websockets. A manual token refresh logic had to be implemented since the OAuth2 client and the websocket client are separate entities and cannot be clubbed together.

(cherry picked from commit 4244fa2)
@mergify mergify bot requested a review from a team as a code owner January 7, 2025 16:39
@mergify mergify bot added the backport label Jan 7, 2025
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Jan 7, 2025
@botelastic
Copy link

botelastic bot commented Jan 7, 2025

This pull request doesn't have a Team:<team> label.

@ShourieG ShourieG enabled auto-merge (squash) January 7, 2025 16:45
@ShourieG ShourieG merged commit 56f3599 into 8.16 Jan 7, 2025
20 of 22 checks passed
@ShourieG ShourieG deleted the mergify/bp/8.16/pr-42212 branch January 7, 2025 18:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@ShourieG ShourieG ShourieG approved these changes

Assignees

@ShourieG ShourieG

Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@ShourieG