Requesting a global OAuth client for a Zendesk Support integration
This is a continuing discussion about the article Requesting a global OAuth client for a Zendesk Support integration in the developer documentation.
Hi @... -- I would check out this article: Creating and using OAuth tokens with the API
Setting up a global OAuth client is needed if you're thinking of developing a Zendesk Marketplace app that is used by different customers who each have their own unique Zendesk Support subdomain.
To answer you're question, it's up to you to request the customer's subdomain. In this workflow, it's your third-party/remote service that wants to access the customer's Zendesk instance. If this is the case in the integration that you're considering to write, it would be this remote service that they would be logged into (some sort of admin portal probably) that then asks for their Zendesk subdomain, that then does the OAuth grant flow steps.
In the end, a "global" OAuth client is just another OAuth client -- the advantage is that you don't have to ask each separate customer to set it up -- it's already set up for them. Meaning that this is really just a convenience feature.
Hi @... @... @... After I apply for the global client,How should I use this client to authorize user_domain?
How to pass the parameters of the authorization link, and whether the access domain is the user's domain or the global domain, If it is a global domain, how should the user domain be passed to the authorized link
In addition, how is example_prompt.png triggered, and what are the links before and after the trigger?
Thank you very much！
There is no any submit form now, but a link only:
Is the procedure changed? I can't see how to do it on the page linked, just our already submitted apps.
I've already found the solution - the form is here now https://apps.zendesk.com/organization
Hi Михаил! If you already have a global OAuth, you will not see the option to request it. Can you confirm whether or not your subdomain already has this associated with the account?
Great to hear that! I'll put in a note to the documentation team to update that page to include some more detailed instructions as well. Thanks for the update!
The documentation page still isn't updated - I had to do a lot of searching to find this link, which appears broken now anyway - if you navigate to https://apps.zendesk.com/organization you just get a blank white page. Frustrating how difficult Zendesk makes it to build apps into your ecosystem.
Sorry this post got missed. This is good feedback and I'll make sure that our docs team takes it into account. Just so I can make sure that this gets into the right hands, which documentation page are you referring to?
Have a wonderful day!
Eric Nelson | Manager - Developer Advocacy
I have created 3 OAuth clients: prod, dev, and staging because each of them has a different redirect URL and I read in the developer documentation that the global clients can only be edited by the platform team after being a global client. I sent the form to change these 3 to global OAuth clients but just read in a comment that after having one you can't request another one?, is there a way to have many global auth clients? or which is the best way to handle different URLs redirection with it?
I'm assuming you wouldn't want your customers to be using the dev or staging versions of your application. Due to that wouldn't you just want to have your dev and staging versions using local oAuth? The pattern and auth method that it uses is the same as global oAuth so you'd be safe from a testing perspective.
Iniciar sesión para dejar un comentario.