-
Notifications
You must be signed in to change notification settings - Fork 74
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
Pass user and password when connecting to server #48
Comments
In principle, yes. I guess we could add optional arguments |
So I won't include this until someone provides a rationale for why this is useful. As it stands, the test suite (of this library) tests local client–server connections. This works without ever providing user credentials, and it works out of the box even on a fresh Comsol installation. I like when things "just work". There is certainly a case to be made for why this is needed for remote client–server connections. So somebody please make that case. Until then, let's not give people incentives to hard-code user credentials in their programs. Because that's how these things leak. |
Hey there, I might be able to weigh in here. I like to run my simulations on the server, while all the outputs and the good stuff just run locally on my laptop. I usually just forward a ssh tunnel from the mphserver running on the server and do the rest locally. This would be an application for a remote client-server connection. |
Hi Killian, thanks for chiming in. The use case is clear to me though. I'm rather wondering why the I may misunderstand this completely though. I never had a chance to test this, and the Comsol documentation doesn't really explain what That being said, there's already a way to do it with the current library code, it's just not documented. (Intentionally. Though I had it in mind the last time I refactored this part of the code.) If I remember correctly, you skip |
Hi,
I have hardcoded together a hack, but can the other connect() options be included:
ModelUtil.connect(<host>,<port>,<user>,<password>)
as an example.
The text was updated successfully, but these errors were encountered: