I apologize in advance for unsolicited pull request, but if possible I would like some advice on whether this is a right approach and maybe I can contribute to the project.
Use-case
I would like to enable authentication on both - H2O and Steam. However, I was unable to find a way for Steam to connect to H2O when (hash) authentication is enabled.
This pull request
Is a proof-of-concept support for connecting to authenticated H2O cluster.
To see it in action (assuming H2O with authentication is running on 127.0.0.1:54321):
Upon clicking "Connect" it should show list of dataframes, retrieved from H2O cluster with authentication.
Caveats
The password is stored in the database file in plain text.
Currently only GetDatasetsFromCluster and RegisterCluster functions use authentication.
Questions
Does this look like a reasonable approach for the above defined use-case? If so and if this PR has a potential to be merged into master branch, I would be happy to accept your guidance on what would be needed from my side to get it done.
I apologize in advance for unsolicited pull request, but if possible I would like some advice on whether this is a right approach and maybe I can contribute to the project.
Use-case
I would like to enable authentication on both - H2O and Steam. However, I was unable to find a way for Steam to connect to H2O when (hash) authentication is enabled.
This pull request
Is a proof-of-concept support for connecting to authenticated H2O cluster.
To see it in action (assuming H2O with authentication is running on
127.0.0.1:54321
):make
the steam binarymake db
./steam serve master --superuser-name admin --superuser-password admin123
./steam login 127.0.0.1:9000 --username admin --password admin123
./steam register cluster --address 127.0.0.1:54321 --username h2ouser --password h2opass
Now opening up http://localhost:9000/ should show the cluster in the list:
Upon clicking "Connect" it should show list of dataframes, retrieved from H2O cluster with authentication.
Caveats
GetDatasetsFromCluster
andRegisterCluster
functions use authentication.Questions
Does this look like a reasonable approach for the above defined use-case? If so and if this PR has a potential to be merged into master branch, I would be happy to accept your guidance on what would be needed from my side to get it done.
Looking forward to hear back from you.