Hi, my organization is trying to Integrate telehealth. It is purchasedan a JWT is active. Working on getting custCreate enabled. I followed the medium article, and will most likely do encryption of URL using C# in an SSIS package. The issue is the encryption. The key we have been given is 36 bytes, way to long for AES 128 specified in the article. As such, I am having trouble even testing the encryption. The website used for encryption in the article is the only site that accepts a key of that length. Is the nonce part of the key? Has the AES-GCM change altered the process? Do we have examples on the encryption? I have seen references to GitHub/zoom/zoomUtils and that is now a dead link. Please help!
Good question. For the Telehealth integration, we only support AES 128 bit encryption.
Are you referring to the API Key? Make sure it is from a JWT App.
Hi Tommy thanks.
I think I figured it out. Using the AES site linked in the medium article I looked at the actual code. It truncates the key. Doing this, I rewrote the code in C# for my workflow and was able to decrypt using their java example.
One question I have is :
Should we be calling applications.zoom in the URL or just zoom.us? The former gives an API key error and the latter gives a decrypt error.
I have emailed isv@zoom twice with no response to get custCreate enabled. Can you help with that? I can PM you our enterprise/telehealth info, just let me know.