You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Dylan Millikin (JIRA)" <ji...@apache.org> on 2015/10/21 14:14:27 UTC

[jira] [Commented] (TINKERPOP3-634) Configurable Graph Hiding in Gremlin Server

    [ https://issues.apache.org/jira/browse/TINKERPOP3-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966719#comment-14966719 ] 

Dylan Millikin commented on TINKERPOP3-634:
-------------------------------------------

Just a train of thought but would it make sense to keep this type of behavior for some authorization feature? It definitely sounds like what you would expect from authorization.

> Configurable Graph Hiding in Gremlin Server
> -------------------------------------------
>
>                 Key: TINKERPOP3-634
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP3-634
>             Project: TinkerPop 3
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.0.1-incubating
>            Reporter: stephen mallette
>            Assignee: stephen mallette
>
> A user may want to configure a {{Graph}} to only be bound to the server for purpose of creating a {{TraversalSource}} and server-driven transaction management.  In this way, the user can "secure" their {{Graph}} locking it down behind the {{TraversalSource}}.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)