We host our applications on Azure and I had to make my deauthorization endpoint an Azure serverless function because the application is only accessed by customer’s subdomain (e.g., customera.presence.io, customerb.presence.io) so I can’t create an endpoint like https://presence.io/zoomdeauth.
Because it’s a serverless application that’s handling the deauthorization, it has an azuredomain (*.azurewebsites.net)
How can I get around this?
The following URLs do not belong to the domain specified above
Which App Type (OAuth / Chatbot / JWT / Webhook)?
It’s an OAuth app that has webhooks.
The deauthorization endpoint.
How To Reproduce (If applicable)
Steps to reproduce the behavior:
- Make the deauth endpoint different.
- See error when submitting for review.
Screenshots (If applicable)
I also use GCP and the domain is different.
https://mydomain.com // valid domain
https://region-mydomain.cloudfunctions.net/unauthorized // here is endpoint url
Please tell me how to resolve it.
Hey @Toshi, @jeffatpresence,
Can you set the deauth url to match the base url, and then route the deauth request based on the account ID in the payload to the proper sub domain customer endpoint?
Let me know if that doesn’t make sense.
I worked with our DevOps person and figured out how to use our domain with my serverless functions so we’re good now. Thanks @tommy!
Great! Happy to hear you got it figured out!
Please let me know if you have any other questions!
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.