在 2012年1月3日 下午7:41，Gordon Sim <[email protected]> 写道： > On 12/23/2011 03:57 AM, tkdchen wrote: >> >> Hi all, >> >> I'm using python-qpid to integrate message bus with a django site. The >> site must connect a QPID broker in a kerberos enviroment, so I pass >> sasl_mechanisms='GSSAPI' to Connection to construct an instance. >> As the subject, I want to know when the script runs on server, whether >> the /etc/krb5.keytab can be discovered automatically, or there is >> something else need to be done via extra Python script codes. > > > I believe you will still have to kinit to obtain a ticket. You can specify > the key tab to use with the -t option to kinit. >
Yes. This is my solution now. I have to run kinit to put ticket into the credential cache /tmp/krb5cc_[uid] regularly, and I decided to do this task in crontab. Thanks! BTW: according to my understand to the Kerberos V5 documentation on the keytab file, the default krb5.keytab exists for service and host server, and it should have been discovered by GSSAPI or other API in my opinion, but it seems that doesn't work like what I thought. :) > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
