[
https://issues.apache.org/jira/browse/KUDU-3415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17633688#comment-17633688
]
Marton Greber commented on KUDU-3415:
-------------------------------------
I tried to repro the issue without any success. Here is my setup:
Kudu cluster: 1 master, 2 tservers. 1 dns server, where I even have a CNAME for
the master.
In the krb5.conf I set rdns = false.
Then I execute the [Kudu java
example|https://github.com/martongreber/kudu/tree/master/examples/java/java-example]
.
But with the above setup, it goes successful. Does my setup resemble the setup
where the error happened?
If not could you please provide details to repro this issue?
> Kerberos authentication fails with rdns disabled
> ------------------------------------------------
>
> Key: KUDU-3415
> URL: https://issues.apache.org/jira/browse/KUDU-3415
> Project: Kudu
> Issue Type: Bug
> Components: client
> Reporter: Abhishek Rawat
> Priority: Major
>
> Kudu Java client doesn't retain the original hostname and replaces them with
> the resolved IPAddress in the kerberos principal. This results in error such
> as following:
> {code:java}
> error Message is Server not found in Kerberos database
> cTime is Sat Jul 28 22:29:26 UTC 2018 1532816966000
> sTime is Thu Oct 27 00:35:03 UTC 2022 1666830903000
> suSec is 129588
> error code is 7
> crealm is CDW-KUDU.XCU2-8Y8X.DEV.CLDR.WORK
> error Message is Server not found in Kerberos database
> crealm is CDW-KUDU.XCU2-8Y8X.DEV.CLDR.WORK
> cname is
> hive/[email protected]
> sname is kudu/[email protected]
> msgType is 30
> cname is
> hive/[email protected]
> sname is kudu/[email protected]
> msgType is 30
> KrbException: Server not found in Kerberos database (7) - LOOKING_UP_SERVER
> {code}
> [~aserbin] suggested this might require the fix done on cpp client side in
> KUDU-2032 to be extended to Java client also.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
