Github user vtslab commented on the issue:
https://github.com/apache/tinkerpop/pull/534
Yes, I mentioned these failing tests in the PR text above. I suspect that
the java security libs just pick up the krb5.conf file from the test resources
"without asking". It means the test fails faster and tries to find credentials
elsewhere when not provided. To resolve it, we either have to adapt the test or
we have to try to configure Kerberos without a krb5.conf file (if that is the
cause). Either way, it does not file nice if test outcomes depend on
unnecessary components being on the classpath or not, so maybe we should look
for a third way.
PR title should be OK now.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
