RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 636841 - Cannot configure kerberos multi realm kadmin/kpropd.
Summary: Cannot configure kerberos multi realm kadmin/kpropd.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: krb5
Version: 7.0
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: ---
Assignee: Nalin Dahyabhai
QA Contact: BaseOS QE Security Team
URL: http://krbdev.mit.edu/rt/Ticket/Displ...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-23 13:17 UTC by Bruno Travouillon
Modified: 2015-04-03 12:43 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 592884
Environment:
Last Closed: 2015-04-03 12:43:20 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Bruno Travouillon 2010-09-23 13:17:21 UTC
+++ This bug was initially created as a clone of Bug #592884 +++

Created attachment 414505 [details]
/etc/init.d/kadmin patch including multirealm support

Description of problem:
Cannot configure kerberos multi realm kadmin/kpropd via standard sysconfig way.
There is no option for using multiple realms on kerberos.

Version-Release number of selected component (if applicable):
krb5-server-1.6.1-36.el5_4.1

Actual results:
Cannot configure

Expected results:
Configuration available

Additional info:

ad1)
If one wishes to use multiple realms on the same host, configration of krb5kdc is no problem. I have to put this

KRB5KDC_ARGS="-r REALM1 -r REALM2"

into the /etc/sysconfig/krb5kdc file, no problem here

ad2)
When someone wants to run kadmin above these two domains, it is necessary to run kadmin standalone on different port for each realm. fe.

/usr/kerberos/sbin/kadmind -r REALM1 -port 749
/usr/kerberos/sbin/kadmind -r REALM2 -port 748

there is no configuration option to do this.

ad3)
When someone wants to propagate multiple realms kerberos database to other kdc hosts, one should run something like this on the slave host

/usr/kerberos/sbin/kpropd -S -r REALM1 -P 754
/usr/kerberos/sbin/kpropd -S -r REALM2 -P 753

there is no configuration option to do this.

Suggested solution:
Add configuration file for kpropd (which does not exists at this time) and put some MULTIPLEREALM variable into this file and kadmin configuration file, edit init scripts for kpropd and kadmind

Example configuration files
/etc/sysconfig/kprop
KPROP_ARGS=
MULTIREALMS="REALM1:754 REALM2:753"

/etc/sysconfig/kadmin
MULTIREALMS="REALM1:749 REALM2:748"

Diffs according to this feature (/etc/init.d/{kprop,kadmin}) are included in the attachment.

Same bug on RHEL6 beta r2

Comment 2 Dmitri Pal 2010-10-13 16:10:11 UTC
We talked with the MIT team. They understand the issue but since it can be easily worked around on one hand with the init scripts and quite a lot of work on the other to implement inside kpropd/kadmin this issue is considered a lower priority than other work currently planned for MIT Kerberos. We will continue tracking this issue for the future releases of Kerberos in RHEL.

Comment 4 Dmitri Pal 2015-04-03 12:43:20 UTC
We have been carrying this bug for quite a while. It is time to admit that until MIT decides to fix it we are not going to do anything about it. Thus I am closing it. If you disagree with this decision do not hesitate to reopen.


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