422 Unprocessable Entity when using request proxy

5 댓글

  • Greg Katechis
    Zendesk Developer Advocacy

    Hi Luis! There are many possible reasons that you could be getting a 422 in this scenario, so it's hard to say from this code snippet. What Zendesk subdomain are you making this request from? I might be able to find something in our logs to provides some additional details.

     

    0
  • Luis Pessoa

    Hi Greg!

    I am using our sandbox environment with subdomain yapecrm1673879820. The app itself is a simple sidebar application with one button that triggers the above mentioned call

    0
  • Greg Katechis
    Zendesk Developer Advocacy

    Thanks for that! From what I can see, it's saying that the token has expired. Can you confirm that if you generate the token manually and make a manual call with a Bearer auth header that it does not work either?

    0
  • Luis Pessoa

    Hmm.. the target is a fake URL .. in theory it should return a network error instead of an expired token. 
    Does the proxy check the JWT itself before making the call to the target endpoint? Another question is shouldn't the proxy refresh the token if applicable (Okta returns all the required fields during the OAuth setup)

    0
  • Luis Pessoa

    Greg-Katechis any news regarding this one?

    0

댓글을 남기려면 로그인하세요.

Zendesk 제공