Enable OAuth on Google connectors#259528
Merged
lorenabalan merged 5 commits intomainfrom Mar 26, 2026
Merged
Conversation
lorenabalan
added
backport:skip
erikcurrin-elastic
approved these changes
Mar 25, 2026
| @@ -35,7 +35,17 @@ export const GmailConnector: ConnectorSpec = { | |||
| supportedFeatureIds: ['workflows'], | |||
| }, | |||
| auth: { | |||
Contributor
There was a problem hiding this comment.
Should we add EARS now? Or can we have a way to add it based on a FF?
Contributor
Author
There was a problem hiding this comment.
Not yet until #253695 is merged. Then, when we start enabling it, it will have to be behind a feature flag.
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
|
jeramysoucy
pushed a commit
to jeramysoucy/kibana
that referenced
this pull request
Apr 1, 2026
## Summary Closes elastic/search-team#13425 Closes elastic/search-team#13424 Tested locally by auth via Elastic-owned app, connectors authz completes successfully and workflows pass as expected. ❓Not sure if we need to any extra documentation anywhere?! **Release note:** Enabled OAuth for authorising Google Connectors (Google Drive, Gmail, Google Calendar). Users can now authorise using their own [Google OAuth Client](https://support.google.com/cloud/answer/15549257?hl=en). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
paulinashakirova
pushed a commit
to paulinashakirova/kibana
that referenced
this pull request
Apr 2, 2026
## Summary Closes elastic/search-team#13425 Closes elastic/search-team#13424 Tested locally by auth via Elastic-owned app, connectors authz completes successfully and workflows pass as expected. ❓Not sure if we need to any extra documentation anywhere?! **Release note:** Enabled OAuth for authorising Google Connectors (Google Drive, Gmail, Google Calendar). Users can now authorise using their own [Google OAuth Client](https://support.google.com/cloud/answer/15549257?hl=en). ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [x] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [x] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [x] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Closes https://github.com/elastic/search-team/issues/13425
Closes https://github.com/elastic/search-team/issues/13424
Tested locally by auth via Elastic-owned app, connectors authz completes successfully and workflows pass as expected.
❓Not sure if we need to any extra documentation anywhere?!
Release note: Enabled OAuth for authorising Google Connectors (Google Drive, Gmail, Google Calendar). Users can now authorise using their own Google OAuth Client.
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:*label is applied per the guidelinesbackport:*labels.