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