애플리케이션에 OAuth 인증 사용하기

image avatar

Charles Nadeau

Zendesk Documentation Team

2025년 5월 20일에 편집됨

15

0

댓글 64개

날짜
    최신순
      image avatar

      Mick Cunningham

      Hi folks! I have this flow working perfectly - only I have had some users state that they normally login to Zendesk via SSO or Google. Right now my OAuth flow requires them to sign in with username and password - and in some cases - users dont remember their login/password ha! Is there any way to quickly add these methods ? Or do I need to develop that from start to finish? Thanks!

      0

      image avatar

      Atha Parveen

      HI Team, 

      I am using my global identifier as the subdomain instead of subdomain, but nothing is working. Can someone help please ?

      0

      image avatar

      Tipene Hughes

      Hey Anish,
       
      Here's a link to the docs on third-party OAuth tokens. Let me know if this helps at all!

      0

      image avatar

      SPARTAN

      Hi Greg Katechis,

      We have been trying to create a channel app where we are attempting to implement OAuth with a third-party application.
      As expected, we have been granted the code to our redirect URL and we generated the access token, but I am clueless as to where I can find information on how to redirect back to the admin UI in the channel app automatically once the OAuth process is completed.
      Could you please help me on this

      0

      image avatar

      Dane

      Hi Robert,

      Our Product Team is already aware of this behavior and is actively working on a fix. As of the moment, we don't have an ETA for it. 

      0

      image avatar

      Robert Hung

      Hello! I have tested the two endpoints for revoking token, and noticed the one ending with /current does not work as expected. I get a 204 response, but I can continue using the same token for future requests.

      I did a comparison of the other revoke endpoint that requires you to pass in the /{oauth_token_id} and this works as expected - all subsequent requests return with a 401 unauthorized.

      Is this expected, or am I missing something?

      I would prefer to use that endpoint because the access token we provide does not have full read scopes, preventing the use of the show token endpoint to retrieve the oauth_token_id and revoke using the working endpoint.

      0

      image avatar

      Mike DR

      HeyA Walter! Did check our list of scopes here: OAuth Tokens for Grant Types but there's not a way to exclude the delete capability as it's included in the write scope.

      0

      image avatar

      Alex

      For generate token i use link https://{{sub-domain}}.zendesk.com/oauth/tokens
      after that try send request to endpoint https://api.getbase.com/v2/leads
      and receive response:

      "error": {
      "code": "unauthorized",
      "details": "Required access token is missing, malformed, expired, or invalid.",
      "message": "request is unauthorized"
      },
      Where problem? how it fix? i asked twice to support but did not receive suggestion

      0

      image avatar

      Walter

      Hi Dane

      Is there anyway to prevent the delete capability when I need the write scope for tickets and users?

      0

      image avatar

      Dane

      Hi Prashant,

      This error means that you are not using a valid token. It's possible that instead of an OAuth, you are just using an API token. Please try to follow the steps again and contact our support directly if you encounter the same issue. 

      0

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

      계정 세부 정보

      세부 정보를 보려면 로그인하세요.

      로그인하여 계정 세부 정보를 한 눈에 확인하세요.

      로그인

      추가 콘텐츠

      자세히 알⁠아⁠보⁠기
      Tips to use API and SDK