You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want to switch from vite-plugin-basic-ssl to vite-plugin-mkcert for the added ability to install the root certificate to other devices.
However, we face a blocker: vite-plugin-mkcert asks for a sudo password during the creation of the certificate on Mac, while it displays a dialogue on Windows. Since we're calling npm run dev from a visual interface, users can't securely enter passwords into the shell, and that prevents us from using it on Mac.
Suggested solution
Not entirely sure. Could a visual UI also be shown on Mac OS to ask users for the password / permissions? My guess is that this could also allow using Touch ID instead of the passwort, but I'm not entirely sure.
Alternative
Ask users to run a command line command when they otherwise work completely in a GUI environment.
Additional context
We considered using mkcert directly (instead of the vite plugin) but the added convenience of not having to specify the location of the cert is great to have for non-technical users.
The text was updated successfully, but these errors were encountered:
Clear and concise description of the problem
We want to switch from vite-plugin-basic-ssl to vite-plugin-mkcert for the added ability to install the root certificate to other devices.
However, we face a blocker: vite-plugin-mkcert asks for a sudo password during the creation of the certificate on Mac, while it displays a dialogue on Windows. Since we're calling npm run dev from a visual interface, users can't securely enter passwords into the shell, and that prevents us from using it on Mac.
Suggested solution
Not entirely sure. Could a visual UI also be shown on Mac OS to ask users for the password / permissions? My guess is that this could also allow using Touch ID instead of the passwort, but I'm not entirely sure.
Alternative
Ask users to run a command line command when they otherwise work completely in a GUI environment.
Additional context
We considered using mkcert directly (instead of the vite plugin) but the added convenience of not having to specify the location of the cert is great to have for non-technical users.
The text was updated successfully, but these errors were encountered: