directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lin Zeng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRKRB-645) Start KerbyKdcServer should be failed if kdc_port already in use
Date Mon, 07 Aug 2017 10:06:01 GMT

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

Lin Zeng commented on DIRKRB-645:
---------------------------------

Hi [~jiajia], I have tested this case, the issue didn't happen when using DefaultInternalKdcServerImpl:).

> Start KerbyKdcServer should be failed if kdc_port already in use
> ----------------------------------------------------------------
>
>                 Key: DIRKRB-645
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-645
>             Project: Directory Kerberos
>          Issue Type: Bug
>            Reporter: Lin Zeng
>            Assignee: Lin Zeng
>         Attachments: DIRKRB-645-01.patch
>
>
> Now user can start KerbyKdcServer successfully if kdc_port already in use, and without
any error information printed in the console. Then when user run kadmin tool, it will hang
there and get the following error after time out:
> {quote}
> Debug is  true storeKey true useTicketCache false useKeyTab true doNotPrompt true ticketCache
is null isInitiator true KeyTab is /home/lonnie/文档/IdeaProjects/directory-kerby/kerby-dist/kdc-dist/conf/admin.keytab
refreKrb5Config is true principal is kadmin/EXAMPLE.COM@EXAMPLE.COM tryFirstPass is false
useFirstPass is false storePass is false clearPass is false
> Refreshing Kerberos configuration
>                 [Krb5LoginModule] authentication failed 
> Receive timed out
> Could not login with: kadmin/EXAMPLE.COM@EXAMPLE.COMReceive timed out
> {quote}
> I think start KerbyKdcServer should be failed if kdc_port already in use.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message