We currently call Gremlin Server without any authentication headers. While this gets the job done, it would be nice to support some form of authentication method in case users deploy the application to a managed service (e.g. Cloud Run) or want to integrate the API with a hosted Gremlin-compatible database such as AWS Neptune.
One option for this would be to abstract out logic for generating Gremlin DriverRemoteConnection objects and allow users to specify these when starting the API server. (e.g. by specifying a name with a flag like --connection-factory my.custom.GremlinConnectionFactory or something similar).
We currently call Gremlin Server without any authentication headers. While this gets the job done, it would be nice to support some form of authentication method in case users deploy the application to a managed service (e.g. Cloud Run) or want to integrate the API with a hosted Gremlin-compatible database such as AWS Neptune.
One option for this would be to abstract out logic for generating Gremlin
DriverRemoteConnection
objects and allow users to specify these when starting the API server. (e.g. by specifying a name with a flag like--connection-factory my.custom.GremlinConnectionFactory
or something similar).