You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kai Zheng (JIRA)" <ji...@apache.org> on 2016/12/06 11:11:25 UTC

[jira] [Commented] (DIRKRB-615) Can not connect to simplekdc server

    [ https://issues.apache.org/jira/browse/DIRKRB-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15724871#comment-15724871 ] 

Kai Zheng commented on DIRKRB-615:
----------------------------------

Hello John,

I'm not sure about how your suggestion would fix the issue, but guess a simple fix could be, have the KDC server started with both TCP and UDP opened?

> Can not connect to simplekdc server
> -----------------------------------
>
>                 Key: DIRKRB-615
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-615
>             Project: Directory Kerberos
>          Issue Type: Bug
>    Affects Versions: 1.0.0-RC2
>            Reporter: John Zhuge
>
> Started a simplekdc server which generated the following krb5.conf:
> {code}
> [libdefaults]
>     kdc_realm = EXAMPLE.COM
>     default_realm = EXAMPLE.COM
>     udp_preference_limit = 1
>     kdc_tcp_port = 10088
>     #_KDC_UDP_PORT_
> [realms]
>     EXAMPLE.COM = {
>         kdc = localhost:10088
>     }
> {code}
> But kinit failed to connect to simplekdc server on Mac:
> {noformat} 
> $ kinit jzhuge
> jzhuge@EXAMPLE.COM's password: 
> kinit: krb5_get_init_creds: unable to reach any KDC in realm EXAMPLE.COM, tried 1 KDC
> {noformat}
> Wireshark showed kinit used UDP, while simplekdc was configured with TCP. Replaced the {{kdc}} option in krb5.conf with {{kdc = tcp/localhost:10088}}, kinit was able to connect.
> Suggested fix:
> Add {{<service>/}} prefix to option {{kdc}} in the template https://github.com/apache/directory-kerby/blob/trunk/kerby-kerb/kerb-simplekdc/src/main/resources/krb5-template.conf and https://github.com/apache/directory-kerby/blob/trunk/kerby-kerb/kerb-simplekdc/src/main/resources/krb5_udp-template.conf.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)