fjmacagno opened a new issue, #64589:
URL: https://github.com/apache/airflow/issues/64589

   ### Apache Airflow Provider(s)
   
   zendesk
   
   ### Versions of Apache Airflow Providers
   
   zendesk 4.11.2
   
   ### Apache Airflow version
   
   2.11.0
   
   ### Operating System
   
   Ubuntu, OSX
   
   ### Deployment
   
   Official Apache Airflow Helm Chart
   
   ### Deployment details
   
   Error is occurring in local development on docker.
   
   ### What happened
   
   I am trying to update to the latest version of the zendesk provider, but 
running into auth problems. Trying to connect to zendesk with a token is 
failing with `zenpy.lib.exception.APIException: {"error": "Couldn't 
authenticate you"}`. The same host/user/password connection field combo works 
fine with the zdesk version of the provider (2.x), so i know the creds are good.
   
   ### What you think should happen instead
   
   I suspect the problem is that the provider only supports "password" auth, 
which is now [deprecated](https://github.com/facetoe/zenpy/issues/651). In 
particular, the init line `Zenpy(domain=domain, subdomain=subdomain, 
email=conn.login, password=conn.password)` in the hook suggests this, zenpy can 
take a "token" parameter instead. The connection should have a way to specify 
that the password fields is a token instead of a password, either with a new 
field or an extra arg or something.
   
   ### How to reproduce
   
   Use a token for authentication using the latest version of the zendesk 
provider and attempt to run any api command.
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to