最近搜索


没有最近搜索

App authentication workflow



已于 2025年3月04日 发布

Hello!

 

I'm building an app to help agents write good answers (an support app).

 

I'm not sure how the authorization workflow looks like for my solution. I have two components:

1. During installation I need a refresh token/api key to migrate data daily

2. During usage (support/ticket_editor) I just need to use ZAF to get current ticket (this I have working)

 

I need a help with components 1.

As far I understand I need to:

1. Get global oauth client

2. Somehow get refresh token/api key during app installation ← I couldn't find materials covering this part

3. Store it somewhere and use when needed

 

Thanks for any advices how to solve this :)

 


1

2

2 条评论

image avatar

Greg Katechis

Zendesk Developer Advocacy

Hi Jacek! We actually do the refreshing for you, so there is no need for a refresh token in this flow. The one caveat is that the access token response must include `expires_in` and `refresh_token` values, which you can read about here.

0


For component 1, you'll need to set up an OAuth flow during installation. First, register a global OAuth client in Zendesk, then prompt the user to authorize the app, which will return an authorization code. Exchange this for a refresh token and store it securely for daily data migration. Zendesk's OAuth documentation should provide more details on this process. 

0


请先登录再写评论。

找不到所需的内容?

新建帖子