-
Notifications
You must be signed in to change notification settings - Fork 168
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
Issue 40 follow up, MacOS native support #554
Comments
Bump! Such a miscalculation to advertise IAP tunneling for RDP but releasing the client for Windows only. |
It would be nice to also have native Linux support as well, even if it involves essentially rewriting the app from scratch. A full featured desktop IAP access client for ssh and rdp is exactly what most sysadmins need to be able to do their work effectively in google cloud. Using the gcloud command line tools and/or the web console is often clumsy/awkward to work with. I just found this desktop app today and it's great, it just needs some polishing up and some modern ssh terminal client features added to it. I understand that this isn't an officially supported google product but it would sure be nice if they would make something like this, or adopt this code as a starting point and build from there. |
Are there any updates on MacOS Support? |
There are still no firm plans for a Mac version of IAP Desktop. I hope that'll change, but at least for now the focus remains on Windows. |
anyone tried running this under WINE emulator (on linux or mac)? |
When working with non- engineers it's not a good solution to recommend them installing the gcloud SDK and starting a local proxy ... Having a UI would be game changer! |
Keep in mind that this is basically just a side project, it's not an official Google project. They really should just do their own cross-platform desktop client for IAP access at some point, it would make a lot of sense. |
We would like a Macos client as well. |
Same, any updates |
This is a follow up on Issue #40, which was addressed with a workaround and closed, but no real fix.
The workaround above is helpful, however this is far from ideal for non-technical users who are accessing VDI sessions over RDP from MacOS clients.
We do this at scale with hundreds of users, and hove clients now doing the same, and this is a significant pain point. mpancottine@google.com can speak to the scale of our deployment and the need for this to be addressed on both Intel and M1 based architectures.
The text was updated successfully, but these errors were encountered: