I think authorization would be a helpful addition for some users so in that
sense I'm in favor of such a feature. I"m mostly concerned with the "how"
part and the interfaces we expose to make it happen. I think I'd be in
favor of a solution that was

* interface/plugin based
* not terribly prescriptive in terms of functionality
* lacking a production-ready reference implementation

Basically, it would be great if we took what we might currently prescribe
as a best practice for authorization and turned it into something easily
implemented by a provider or user. It should be less hard to implement than
writing a custom Channelizer with custom Netty handlers but be more effort
than just tinkering with configuration files.

I realize that's all very high-level, but I just wanted to express my
thoughts on what I think Gremlin Server should offer in this area as
"authorization" has a really wide surface area as a feature.



On Thu, Jun 11, 2020 at 4:14 PM Marc de Lignie <[email protected]>
wrote:

> For a specific use case in my employer's organization I did some initial
> work on opening up Gremlin Server to authorization plugins. It would
> certainly be stimulating to enable a wider audience to use this work by
> contributing it to Apache TinkerPop. But I realize that, given the
> complexity of authorization and its dependence on other TinkerPop
> features, it is certainly not obvious that the TinkerPop team would want
> to support it. The more so because of indications that the TinkerPop
> team wants to move to a more focussed re-implementation based on recent
> theoretical and managerial insights (TP4).
>
> To facilitate a discussion whether or not to support authorization for
> Gremlin Server in some way, I have written a concrete proposal published
> at
>
> https://yaaics.blogspot.com/2020/06/proposing-authorization-for-gremlin.html
>
> I hope you can give it some attention and formulate your arguments in
> favor or against it on the dev mailing list, or maybe provide
> perspectives on an alternative proposal.
>
> Best wishes,    Marc
>
>
>
>

Reply via email to