[
https://issues.apache.org/jira/browse/TINKERPOP3-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14966724#comment-14966724
]
stephen mallette commented on TINKERPOP3-634:
---------------------------------------------
yes - that's an interesting thought. i had been hoping that authorization
would get implemented through sandboxing, but sandboxing doesn't cover who can
say what graph, so it stinks that we have these two distinct concepts that
could control security. some bigger thinking on how to unify these things
would be good which is another reason to hold off on this one (at least until
it is all thought through).
> 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)
