Bug 1108225

Summary: ipadb.so could get tripped up by DAL changes to support keyless principals
Product: Red Hat Enterprise Linux 7 Reporter: Martin Kosek <mkosek>
Component: ipaAssignee: Martin Kosek <mkosek>
Status: CLOSED ERRATA QA Contact: Namita Soman <nsoman>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 7.1CC: jgalipea, mkosek, npmccallum, rcritten, rmainz
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ipa-4.0.3-1.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-05 10:11:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Kosek 2014-06-11 14:57:55 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3779

Upcoming changes to upstream krb5 may result in modification requests that get passed into the IPA kdb plugin including a zero-length list of keys, which may or may not be NULL.

We need to make sure that the plugin isn't going to be tripped up by any of this, and that it correctly interprets this as a request from the caller to remove all of the keys from the principal entry (which in LDAP, I assume means removing the attribute value completely).

Comment 1 Martin Kosek 2014-06-11 15:23:27 UTC
This request is already fixed in upstream FreeIPA project. Please refer to the linked ticket for additional details and related commits.

Comment 2 Namita Soman 2014-06-26 05:10:45 UTC
Please add steps to verify

Comment 3 Martin Kosek 2014-06-26 08:24:30 UTC
This patch is about future proofing so that FreeIPA KDC backend is ready for keyless principals. AFAIU, there is no practical reproduction yet (CCing Nathaniel in case I am wrong). I would thus propose to simply test as SanityOnly.

Comment 5 Martin Kosek 2014-07-18 08:04:39 UTC
Please see Comment 3 for reproduction/how to test information.

Comment 13 errata-xmlrpc 2015-03-05 10:11:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0442.html