Bug 591716 - Gray out KDC and admin fields when kerberos parameters are discovered via DNS
Summary: Gray out KDC and admin fields when kerberos parameters are discovered via DNS
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: authconfig (Show other bugs)
(Show other bugs)
Version: 6.0
Hardware: All Linux
low
medium
Target Milestone: rc
: ---
Assignee: Tomas Mraz
QA Contact: Petr Šplíchal
URL:
Whiteboard:
Keywords:
Depends On: 591681
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 21:30 UTC by Dmitri Pal
Modified: 2016-06-01 01:39 UTC (History)
6 users (show)

Fixed In Version: authconfig-6.1.4-2.el6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 591681
Environment:
Last Closed: 2010-11-10 19:55:14 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Dmitri Pal 2010-05-12 21:30:55 UTC
+++ This bug was initially created as a clone of Bug #591681 +++

Description of problem:

After selecting FreeIPA as authentication server in authconfig and marking checkbox 'Use DNS to locate KDC for realms' it would be good that the fields KDCs and 'Admin servers' are grayed out?

Version-Release number of selected component (if applicable):
authconfig-6.1.4-2.fc13.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Just configure FreeIPA authentication with DNS used to locate KDCs.

Additional info:
In /etc/krb5.conf DNS resolution is selected and in the sam time values of KDC and admin server are filled with exact values. The question is which values have higher priority?

--- Additional comment from tmraz@redhat.com on 2010-05-12 16:30:39 EDT ---

According to the krb5.conf manpage the DNS is used only when the realm and KDC is not filled in. I am not sure whether sssd behaves the same.

--- Additional comment from sgallagh@redhat.com on 2010-05-12 16:52:27 EDT ---

Jakub, can you clarify? I think our default behavior is the same, but you're the authority.

Comment 1 RHEL Product and Program Management 2010-05-12 22:05:49 UTC
This feature request did not get resolved in time for Feature Freeze
for the current Red Hat Enterprise Linux release and has now been
denied. You may re-open your request by requesting your support
representative to propose it for the next release.

Comment 2 Dmitri Pal 2010-05-12 23:41:23 UTC
Cleared RFE word fron title and reset the flags.

Comment 3 RHEL Product and Program Management 2010-05-13 00:33:09 UTC
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.

Comment 6 releng-rhel@redhat.com 2010-11-10 19:55:14 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.


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