We have our Android application using AppAuth library with custom tabs for OAuth authorization.
We are using
User login using SSO, and they are redirected to VMware Workspace One SSO client, after user is Authenticated by vmware, zoom SSO page is loaded
vmware.zoom.us/saml/SSO, and in most of the cases this redirects to our
redirect_uri, but in some cases this page don’t load redirect URI but it loads
I have compare a network log for both cases (when redirect_uri and when /meeting) and I can’t determine why is it that some cases we are being redirected to
vmware.zoom.us/meeting instead of the redirect URI.
These are the network trace for when we end in redirect_uri and when we end on /meeting page
Reviewing the .har files we could see that the inflection point on which they start to differ is after user is authenticated by workspace one SSO and calls the zoom SSO to finish the OAuth flow.
We would see
location header and redirectURL pointing to this /meeting for when we have this issue happening.
Hello forum, could someone please take a look to this issue.
Any ideas or suggestion on how to fix it are welcome
I was able to notice that when the authentication flow ends in the
/meetings page, we are missing the
_zm_bu cookie, this is when loading
On the contrary when the flow ends on the redirectURI (the expected result),
_zm_bu cookie is present containing the right
/authorized endpoint with the redirectURI
I found this issue with the same cookie
_zm_bu, but I believe is the opposite case.
We are developing an OAuth user level App to enable integration with our scheduling service. We have everything working except we are seeing a strange behavior during user authentication. When in our application, we direct the user to enable the Zoom integration and authenticate with the OAuth app using the following URL:
(trying to avoid links since I’m a new user, so bear with me)
http:// zoom. us/oauth/authorize?client_id=<our_client_id>&response_type=code&redirect_uri=https:…
Could someone help me find out why if both flow (
meeting redirect.har and
redirect_uri redirect.har) have the same steps but they end on a different page.