SDK initialization requires access to "Zoom Safe Meeting Storage" item in keychain

Meeting SDK macOS
1

Description
After updating to the most recent Zoom SDK release (v5.2), users now receive prompts for keychain access when initializing the SDK. See screenshot below. I encountered these prompts on my project using the Electron SDK, but also was able to reproduce this on the Zoom macOS SDK sample application. Looks like this issue is caused by running both the zoom.us client and SDK apps (or multiple SDK apps) since these apps are competing for keychain access to both the “Zoom Meeting Storage” and “Zoom Safe Meeting Storage” keychain items.

Why are these prompts/keychain access necessary after the latest update? How do we disable these prompts for our users to avoid confusion?

Which version?
v5.2.41735.0929

To Reproduce(If applicable)
Steps to reproduce the behavior:

  1. Install the zoom.us client and setup and run a meeting
  2. Download the latest zoom macOS sample app
  3. Run the sample app and attempt to initialize the SDK
  4. Prompt for confidential info in keychain will appear

Screenshots

Screen Shot 2020-10-10 at 2.28.17 PM
Screen Shot 2020-10-10 at 2.28.17 PM876×438 63.9 KB

Thanks,
Nitin

2 Likes
2

@carson.zoom can you help to solve this? We’re experiencing the same issue.

1 Like
3

Hi @carson.zoom, any update on this one?

Thanks,
Nitin

4

I noticed that this pop up comes even when you start zooms own client. So I think there is little hope that it can be fixed…

5

Any news on this one - it also means that when I move back to the normal zoom client after using my sdk version I have to enter that password - very annoying!

6

Hi @carson.zoom and @tommy,

We really need some guidance and documentation around this. It’s a poor UX for anyone using a zoom SDK app and zoom client. What is the impact of users denying access to those keychain items? How can we ensure that users aren’t prompted constantly by the OS for keychain access when using SDK apps and the zoom client?

Thanks,
Nitin

7

Nitin, Zoom’ stock is at $520. I hope you understand that @carson.zoom and @tommy don’t care what we need anymore :money_mouth_face: :joy:

8

Hi @nraj, @tmiskiew, @richard1 ,

Thanks for the post. Recently we are short of bandwidth here(hopefully more resources are coming), sorry for the late response.

Recently the Zoom client(Added in 5.2) has added a new feature to enhance the encryption on the local database to further protect your information so it triggered this system pop-up. When SDK upgrades to 5.2, it inherits this enhancement.

I understand it is frustrating. Here are 2 action items that I have already done before this reply:

  1. I have asked the SDK team to provide a fix and grab your app name to replace the “Zoom” in the “Zoom Safe Meeting Storage”. We will have a hotfix that provides this interface early next week
  2. I have reported your concerns to the Zoom client team and they will investigate the solution to optimize this scenario and avoid further confusion for you and your user. Once the client team optimizes this, our SDK will inherit the changes.

We do value your concerns and feedbacks. Please feel free to let me know if any other questions.

Thank you.

1 Like
9

@carson.zoom - any update on this?

10

@tmiskiew I believe it’s fixed in v5.2.41751.1026

11

Hi everyone,

We have released a new version that addresses this concern and you may find it here: https://github.com/zoom/zoom-sdk-macos/releases/tag/v5.2.41751.1026

Please have a try. Thanks!

1 Like
12

Hi @carson.zoom, thanks for getting out a new version so quickly, much appreciated! Also appreciate all the details on your previous post, the transparency is very helpful :slight_smile:

Thanks,
Nitin

1 Like
13

@nraj Thank you for your understanding. Sometimes the SDK has some downstream impacts from the changes in the Zoom client but we will try our best to address all the concerns and take actions to resolve the issues.

As this issue has been resolved, I will go ahead and close this post. Please feel free to create another post if any other questions.

Thank you.