Background: In one of our preprod ServiceNow instances I have installed the Zoom 3.0.0 spoke the Notify Zoom Connector 1.3.0. according to our Zoom admin since we use SSO you can only have your email address in Zoom on the preprod side or the prod side but it cannot be in both. Since we want to start by testing I had them use my personal email address on the zoom preprod side that does not flow through Zoom SSO. I followed the instructions for the Zoom Spoke and had issue where I had to open a support case that was resolved since I was not able to get the OAuth Tokens created. We remedied that by having the Zoom admin use their computer, share their screen and I log into SNOW preprod instance with my admin and click Get OAuth token. Once that happened we got the tokens created in SNOW and completed the setup. We assume that since we use SSO his web browser associated to his Zoom login. Otherwise when I clicked "Get OAuth token" on my workstation it had a a popup window that asked me to log into Zoom and when I did said I was not authorized to Approve or Authorize the app or what ever the message was. After all of that I proceeded to follow the instruction for the Notify Zoom connector as per the docs. I then went into Flow Designer created a simple subflow and added the Zoom spoke activity "Create Meeting". There is one required field on the activity "User ID".
If I have tried using "me" and I have also tried my personal email address that was setup in the zoom test environment. both are giving me the same errors: In the Output Data I get "Invalid access token." under the Error Message and i get Method failed: (/v2/users/me/meetings) with code: 401 - Invalid username/password combo.
I consider SSO may be a factor on SNOW side as well as Zoom side. I am using a local admin account on the SNOW side that is non-SSO and i am using a non-SSO email address on the zoom side. I can't figure out why it is saying bad username/password in the error when I am only passing the email address or "me" as the User ID. Also getting the Invalid token is throwing me off since I can see that I have OAuth tokens created in SNOW and it is using it on the Connector Alias as shown in the picture above.
Anyone care to share how they got theirs working. I have been at it a week now with waiting for support and admins to help and I figured this would get much easier after we got stuck not getting the the tokens.
