Oauth redirect_uri which uses the url hash is not supported

it’s just that I found there is an issue when redirect_uri uses hash

the url that I created is:

After doing the authorization process, redirected go back to my site with url pattern => https://example.com/path#zoom?code=xxxxxxx

code url params will be unreadable because it goes into the hash scope
window.location.hash => #zoom?code=xxxxxxx
window.location.search => ""

Which App Type (OAuth / Chatbot / JWT / Webhook)?

Additional context
Btw it’s working if i don’t encode the redirect_uri like this https://zoom.us/oauth/authorize?response_type=code&client_id=xxxxxxx&redirect_uri=https://example.com/path#zoom

then after doing the authorization process, redirected go back to my site with the url pattern =>

with that url pattern, then we can read the param url code:
window.location.hash => #zoom
window.location.search => ?code=xxxxxxx

but without encoding… this goes against the best practice of usage in url params…

Hey @agung.quipper,

Can you try.adding a slash at the end of your redirect url and before the #zoom?

Like this: https://example.com/path/#zoom

Let me know if that fixes the issue! :slight_smile:


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.