Bug 588218 - Feature Request: Allow setting of KRB5_KTNAME for the qpidd init script
Feature Request: Allow setting of KRB5_KTNAME for the qpidd init script
Status: NEW
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: mick
MRG Quality Engineering
Depends On:
  Show dependency treegraph
Reported: 2010-05-03 03:23 EDT by Tim Powers
Modified: 2015-09-07 01:47 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Powers 2010-05-03 03:23:06 EDT
Currently, qpidd defaults to using /etc/krb5.keytab because KRB5_KTNAME cant be set without editing the init script. The problem is that often a host will have multiple keytabs files other than /etc/krb5.keytab. In this case, it would be nice to use /etc/qpidd.keytab or /etc/qpidd.<hostname>.keytab or some other random filename and location.

Two possible ways of adding this support... 

1. Allow setting the krb5 keytab location in /etc/qpidd.conf (ie krb5-ktname=) and have the c++ broker executable set KRB5_KTNAME.

2. While the init script already looks for /etc/sysconfig/qpidd, the sysconfig file should be added to the qpid-cpp package. Also,  and add a test to see if KRB5_KTNAME is set should be added to the init script. If it exists in /etc/sysconfig/qpidd then set it where qpidd is started by daemon().
Comment 1 Gordon Sim 2010-12-13 12:00:01 EST
See also https://bugzilla.redhat.com/show_bug.cgi?id=635585 which is related.

Note You need to log in before you can comment on or make changes to this bug.