The current tests do not include authentication or ssl. I think after we merge the latest driver/driver test changes this should be the next order of business. I would be happy to do a PR.
On Mon, Jan 30, 2017 at 3:19 PM, Stephen Mallette <spmalle...@gmail.com> wrote: > If i remember correctly Marko had wanted to have the two instances > configured with the idea that we would test gremlin-python against both. I > think that remains a work in progress. David Brown has some changes coming > in a PR to tp32 that make some improvements to the tests over there. > Perhaps we can look at getting security hooked up appropriately after that > so that we can get some tests rolling there. > > On Mon, Jan 30, 2017 at 3:16 PM, vtslab <vts...@xs4all.nl> wrote: > >> >> While trying to get gremlin-python to work with the proposed Kerberos >> authenticator for gremlin-server (https://github.com/apache/tin >> kerpop/pull/534), I noticed that gremlin-python's pom.xml starts a >> gremlin-server with SimpleAuthenticator (port 45941) but no tests seem to >> use it, nor are the user= and password= arguments of the >> driver_remote_connection.py ever tested. Is this still work in progress or >> do I miss something? >> >> Possibly related to this, @davebshow remarks about the recenntly >> closed/merged issue https://issues.apache.org/jira/browse/TINKERPOP-1600 >> , that all gremlin-python remote_driver_connection tests pass. Does this >> include username/password authentication for which the netty handler coding >> possibly changed due to TINKERPOP-1600? >> >> Cheers, Marc >> -- David M. Brown R.A. CulturePlex Lab, Western University
