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.

Description of problem:
support for older style generic attributes in rlm_ldap doesn't work.


If I uncomment 2 lines with 
control:   += 'radiusCheckAttributes'
reply: += 'radiusReplyAttributes'

in /etc/raddb/mods-enabled/ldap

then radiusd fails to start with

...
/etc/raddb/mods-enabled/ldap[74]: Invalid source for list '+='
/etc/raddb/mods-enabled/ldap[8]: Instantiation failed for module "ldap"

This problem should be fixed in 3.0.5 version

Version-Release number of selected component (if applicable):
freeradius-3.0.4-4.el7


How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Here is a thread discussing this: http://lists.freeradius.org/pipermail/freeradius-users/2014-October/074288.html

Unfortunately backporting a fix for this to 3.0.4 would be too invasive. We'll have to postpone it to rebase to 3.0.5 or later.

This was fixed in v3.0.9.

Not that the attributes were renamed to radiusCheckAttribute and radiusReplyAttribute correspondingly.

Hi Nikolai,

I can confirm, it is fixed in 3.0.12.

Good news! Thank you, Jaroslav.

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://access.redhat.com/errata/RHEA-2017:1954