You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Lin Zeng (JIRA)" <ji...@apache.org> on 2017/08/07 06:55:00 UTC

[jira] [Created] (DIRKRB-645) Start KerbyKdcServer should be failed if kdc_port already in use

Lin Zeng created DIRKRB-645:
-------------------------------

             Summary: 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


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:

bq. 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

I think start KerbyKdcServer should be failed if kdc_port already in use.




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