Bug 789478 - Provide a new option for different ways of dealing with multi-valued names not matching RDN
Summary: Provide a new option for different ways of dealing with multi-valued names no...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: SSSD Maintainers
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-10 20:59 UTC by Dmitri Pal
Modified: 2020-05-02 16:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-04-24 11:22:20 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2001 0 None None None 2020-05-02 16:23:46 UTC

Description Dmitri Pal 2012-02-10 20:59:56 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/sssd/ticket/959

Some arguably broken LDAP configurations use multi-valued names that don't match the RDN. We need a way to handle with such configurations.

We reduced the scope of #926 to fall back to just picking the first value. This tickets is a RFE for a new option that could be used to pick the name in a different way, perhaps by picking the alphabetically smallest (see https://fedorahosted.org/sssd/ticket/926#comment:1)

Comment 3 Martin Kosek 2015-04-24 11:22:20 UTC
Thank you taking your time and submitting this request for Red Hat Enterprise Linux. Unfortunately, this bug was not given a priority and was deferred both in the upstream project and in Red Hat Enterprise Linux.

Given that we are unable to fulfill this request in following Red Hat Enterprise Linux releases, I am closing the Bugzilla as DEFERRED. To request that Red Hat re-considers the decision, please re-open the Bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.

Note that you can still track this request or even contribute patches in the referred upstream Trac ticket.


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