Added access_token authorization method

[sujitsagar]

What

The problem was that zendesk access_token auth was not available

How

I have added Access Token option in the allowed authorization methods

Recommended reading order

1. x.java
2. y.python

🚨 User Impact 🚨

---

Pre-merge Checklist

Expand the relevant checklist and delete the others.

New Connector

Community member or Airbyter

• Community member? 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
• Documentation updated
  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • docs/SUMMARY.md
  • docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
  • docs/integrations/README.md
  • airbyte-integrations/builds.md
• PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• Credentials added to Github CI. Instructions.
• /test connector=connectors/<name> command is passing.
• New Connector version released on Dockerhub by running the /publish command described here
• After the connector is published, connector added to connector index as described here
• Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here

Updating 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
• Documentation updated
  • Connector's README.md
  • Connector's bootstrap.md. See description and examples
  • Changelog updated in docs/integrations/<source or destination>/<name>.md including changelog. See changelog example
• PR name follows PR naming conventions

Airbyter

If this is a community PR, the Airbyte engineer reviewing this PR is responsible for the below items.

• Create a non-forked branch based on this PR and test the below items on it
• Build is successful
• Credentials added to Github CI. Instructions.
• /test connector=connectors/<name> command is passing.
• New Connector version released on Dockerhub by running the /publish command described here
• After the new connector version is published, connector version bumped in the seed directory as described here
• Seed specs have been re-generated by building the platform and committing the changes to the seed spec files, as described here

Connector Generator

• Issue acceptance criteria met
• PR name follows PR naming conventions
• If adding a new generator, add it to the list of scaffold modules being tested
• The generator test modules (all connectors with -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
• Documentation which references the generator is updated as needed.

[CLAassistant]

All committers have signed the CLA.

[marcosmarxm]

Hello @sujitsagar the PR #7086 is already adding OAuth for Zendesk support, there is anything blocking you with this change? @antixar for your info

[sujitsagar]

Hi @marcosmarxm, yes, its a blocker for us. We can support only Access Token based authorizer for this connector. Enabling it sooner would help us a lot.

cc: @antixar

[antixar]

oAuth2.0 is ready but the Airbyte UI part is not completed for its using. Later your correction will be converted to an oAuth 2.0 button for full oAuth2 flow.

[sujitsagar]

Thanks @antixar. Can I contribute for Airbyte UI part as well?
Can you please point me relevant folder/file? I will make necessary changes.

[antixar]

/test connector=connectors/source-zendesk-support

Error: No ref found for: patch-1

[antixar]

@sujitsagar ,thank you for your activity but UI part has already been being developing now.
I've corrected your PR a bit.
@marcosmarxm please help me to merge this PR to master.

[antixar]

@sujitsagar , could you upgrade to the latest version and test the new auth method?

[sujitsagar]

@antixar I have upgraded and tried this patch. It works great.
Thank you for your support.
cc: @marcosmarxm