[
https://issues.apache.org/jira/browse/TINKERPOP-1566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15831845#comment-15831845
]
ASF GitHub Bot commented on TINKERPOP-1566:
-------------------------------------------
Github user vtslab commented on the issue:
https://github.com/apache/tinkerpop/pull/534
Hi, I am working on the two failing integration tests. It can be fixed in
three ways:
1. just hide the symptoms and also allow a GSSException for a test that
should fail anyway: ugly!
2. configure <useForks>false for the failsafe plugin: fine, but may impact
test performance
3. adapt the gremlin-driver handler code, which now chooses GSSAPI if no
credentials are supplied. This should be a test on an available JaasEntry.
Which of the ones do you like to see committed on the PR?
> Kerberos authentication for gremlin-server
> ------------------------------------------
>
> Key: TINKERPOP-1566
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1566
> Project: TinkerPop
> Issue Type: Improvement
> Components: server
> Reporter: Marc de Lignie
> Priority: Minor
> Labels: security
> Fix For: 3.3.0
>
>
> Gremlin server would benefit from an explicit Kerberos authentication plugin,
> because preparing and maintaining such a plugin is nontrivial. Also, many
> other Apache project provide kerberized services.
> In gremlin-console the standard Krb5LoginModule can be configured.
> Gremlin-server already includes the pluggable Sasl framework that can host
> the proposed Kerberos authentication plugin.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
