[
https://issues.apache.org/jira/browse/TINKERPOP-1263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15250704#comment-15250704
]
ASF GitHub Bot commented on TINKERPOP-1263:
-------------------------------------------
Github user spmallette commented on the pull request:
https://github.com/apache/incubator-tinkerpop/pull/291#issuecomment-212602340
Not sure why but I had to close this PR manually. Looks like the merge went
as it should so.....maybe just some broken automation. I updated changelog and
dev/upgrade docs as well.
> Pass SASL mechanism name through with initial SASL response
> -----------------------------------------------------------
>
> Key: TINKERPOP-1263
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1263
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.1.2-incubating
> Reporter: Mike Adamson
> Assignee: stephen mallette
> Fix For: 3.1.3, 3.2.1
>
>
> Support was added to the client driver to allow either plain text or GSSAPI
> SASL authentication. This improvement is for the client to pass the name of
> the mechanism as part of the initial SASL response. This gives the server
> side SASL handler the option to negotiate whether it will allow the specific
> mechanism.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
