Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[macos] Persist granted permissions #2

Open
devidw opened this issue Sep 23, 2023 · 6 comments
Open

[macos] Persist granted permissions #2

devidw opened this issue Sep 23, 2023 · 6 comments

Comments

@devidw
Copy link

devidw commented Sep 23, 2023

Hey

I am getting this dialog after closing and reopening the macos app

Screenshot 2023-09-23 at 4 37 30 PM

Would there eventually be a way to have the app remember granted permissions?

I guess this is needed for the certificate file access

Thanks

@devidw devidw changed the title Persist granted permissions [macos] Persist granted permissions Sep 23, 2023
@shockerli
Copy link
Owner

This is the file access that is controlled by macOS and can be viewed through System Settings - Privacy & Security - Files & Folders

image

@devidw
Copy link
Author

devidw commented Sep 26, 2023

Hey @shockerli

Thanks for your answer

I can confirm that this perm is granted before app start up, but nevertheless etcq asks for it on every launch

Screenshot 2023-09-26 at 3 42 40 PM

@shockerli
Copy link
Owner

ETCQ automatically connects to each ETCD server each time it is started.

If the HTTPS connection certificate is set, file permissions are requested. You can check whether the three configuration items cert_file, key_file, ca_cert_file are empty, ETCQ config file path is ~/Library/Application\ Support/ETCQ/etcd.json

@devidw
Copy link
Author

devidw commented Sep 27, 2023

Yep that works fine - and i can confirm that the connection and the whole apps works great - also the config file is filled like it should

It's just a bit annoying that the permission needs to be granted on each app launch :D

@shockerli
Copy link
Owner

ETCQ does not collect any private data.

Currently, HTTPS connections directly use the certificate file path specified by the user. Therefore, when the application is launched and connects automatically, it does indeed access the file. The experience can be optimized in the future.

@devidw
Copy link
Author

devidw commented Sep 28, 2023

Gotcha, thanks for clarification, will keep this open - I guess we can close this when you eventually roll out a mechanisms to avoid prompting on each launch

Repository owner deleted a comment Feb 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants