-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Source Zoom: Replace JWT Auth methods with server-to-server Oauth #25308
Source Zoom: Replace JWT Auth methods with server-to-server Oauth #25308
Conversation
airbyte-integrations/connectors/source-zoom/source_zoom/components.py
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR @KqLLL we really appreciate it. We're unable to test this PR without credentials, so we're waiting for those credentials to be generated.
In the meantime, can you bump the versions in the Dockerfile and metadata.yaml for the Zoom connector? Please keep in mind we follow semantic versioning and this would be considered a major change.
I have updated these versions in Dockerfile and metadata.yaml. Just a gentle reminder, if you take some time to study the Zoom API, you might notice that the data provided by the Zoom connector appears to be inaccurate. |
Can please someone merge ? JWT does not exist |
Hello, we're going to prioritize the review of this contribution next week. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello 👋 I'm working to get Airbyte's test account to use the new Oauth method. I'm going to return the review after we get them.
@KqLLL still waiting to have the server-to-server Oauth enabled in our integration account. Hope this week we can have a return. |
The internal ticket created to our infra team was moved to next sprint. Hope to get this unblock next week. @KqLLL are you available to make a call and maybe show me the connector working in your side? |
Ok, I can show a snapshot of my connector working. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you update the documentation with the note and the Changelog with the new version?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some comments and we're good to merge the contribution. I'm still working to get credentials from our side but probably we can merge before that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @KqLLL
/approve-and-merge reason="Today Airbyte doesnt have a separated Zoom account for only tests purpose. User showed their code implementation is working and also its using the low-code. For future I created a Github issue to have a Zoom credentials working" |
…5308) * Replace JWT Auth methods with server-to-server Oauth * Bump versions in the Dockerfile and metadata.yaml
Hi @marcosmarxm @KqLLL, thanks a lot for this work ! Do you have any idea why version 1.0.0 is not in dockerhub ? |
I'm wondering the same. @DiegoPiloni did you see any change? |
@jcolinger3 What I understand is that #30361 still needs to be approved and merged |
What
Describe what the change is solving
Update the Auth method
Resolve Issue #23268
According to the document, the Zoom JWT auth methods will be deprecated on June 1, 2023. The Zoom source connector only supports JWT and will stop working at that time.
https://marketplace.zoom.us/docs/guides/build/jwt-app/jwt-faq/
How
Describe the solution
Recommended reading order
x.java
y.python
🚨 User Impact 🚨
Are there any breaking changes? What is the end result perceived by the user?
For connector PRs, use this section to explain which type of semantic versioning bump occurs as a result of the changes. Refer to our Semantic Versioning for Connectors guidelines for more information. Breaking changes to connectors must be documented by an Airbyte engineer (PR author, or reviewer for community PRs) by using the Breaking Change Release Playbook.
If there are breaking changes, please merge this PR with the 🚨🚨 emoji so changelog authors can further highlight this if needed.
Pre-merge Checklist
Expand the relevant checklist and delete the others.
New Connector
Community member or Airbyter
airbyte_secret
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.0.0.1
Dockerfile
has version0.0.1
README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
including changelog with an entry for the initial version. See changelog exampledocs/integrations/README.md
airbyte-integrations/builds.md
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereUpdating a connector
Community member or Airbyter
Grant edit access to maintainers (instructions)
Secrets in the connector's spec are annotated with
airbyte_secret
Unit & integration tests added and passing. Community members, please provide proof of success locally e.g: screenshot or copy-paste unit, integration, and acceptance test output. To run acceptance tests for a Python connector, follow instructions in the README. For java connectors run
./gradlew :airbyte-integrations:connectors:<name>:integrationTest
.Code reviews completed
Connector version has been incremented
Dockerfile
has updated versionDocumentation updated
README.md
bootstrap.md
. See description and examplesdocs/integrations/<source or destination>/<name>.md
with an entry for the new version. See changelog examplePR name follows PR naming conventions
Airbyter
If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.
/test connector=connectors/<name>
command is passing/publish
command described hereConnector Generator
-scaffold
in their name) have been updated with the latest scaffold by running./gradlew :airbyte-integrations:connector-templates:generator:testScaffoldTemplates
then checking in your changes