You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2017/04/10 19:42:41 UTC

[jira] [Closed] (TINKERPOP-1657) Provide abstraction to easily allow different HttpAuth schemes

     [ https://issues.apache.org/jira/browse/TINKERPOP-1657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stephen mallette closed TINKERPOP-1657.
---------------------------------------
       Resolution: Implemented
         Assignee: stephen mallette
    Fix Version/s: 3.2.5

> Provide abstraction to easily allow different HttpAuth schemes
> --------------------------------------------------------------
>
>                 Key: TINKERPOP-1657
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1657
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: server
>            Reporter: Keith Lohnes
>            Assignee: stephen mallette
>             Fix For: 3.2.5
>
>
> The current HttpChannelizer allows for extension through an Authenticator class supplied through the authorization settings. There isn't, however, an extension point for an authentication handler. Currently the choice is between the `AllowAllAuthenticator` or the `HttpBasicAuthenticationHandler`. One would need to create a new channelizer where the HttpChannelizer would suffice. Creating an abstract class that can be extended would make it easier to extend Authentication for things like token authentication schemes.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)