[
https://issues.apache.org/jira/browse/DIRKRB-645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16116211#comment-16116211
]
Jiajia Li commented on DIRKRB-645:
----------------------------------
Thanks for reporting and providing the patch. I'm not sure whether
DefaultInternalKdcServerImpl has the same issue, could you help to test?
> 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....@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)
