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.
Bug 1167846 - radiusd fails to load clients from ldap
Summary: radiusd fails to load clients from ldap
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: freeradius
Version: 7.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Nikolai Kondrashov
QA Contact: Jaroslav Aster
URL:
Whiteboard:
Depends On: 1202751
Blocks: 1205796
TreeView+ depends on / blocked
 
Reported: 2014-11-25 14:07 UTC by David Spurek
Modified: 2019-03-06 01:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 20:36:03 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:1954 0 normal SHIPPED_LIVE freeradius bug fix and enhancement update 2017-08-01 18:29:54 UTC

Description David Spurek 2014-11-25 14:07:25 UTC 
Description of problem:
radiusd fails to load clients from ldap. remove localhost entry from clients.conf and add it to ldap. radtest then should work.

It will be fine to change ldap filter in clients section. Now is filter set to filter = '(objectClass=frClient)' but freeradius.schema in freeradius-doc has objectclasses radiusObjectProfile and radiusprofile,

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

How reproducible:
always

Steps to Reproduce:
1.echo '' > /etc/raddb/clients.conf 
2.
uncomment 
shortname = 'radiusClientShortname'
nas_type = 'radiusClientType'

in /etc/raddb/mods-enabled/ldap
3. add client localhost entry to ldap

dn: radiusClientShortname=localhost,ou=Clients,dc=example,dc=com
objectclass: radiusClient
radiusClientIdentifier: 127.0.0.1
radiusClientSecret: testing123
radiusClientShortname: localhost
radiusClientType: other

4. service radiusd start
5. try radtest query to localhost, for example
radtest user redhat localhost 0 testing123

Actual results:
radtest fails and radiusd shows following output:

Ignoring request to auth address * port 1812 as server default from unknown client 127.0.0.1 port 55634 proto udp




Expected results:
radtest should pass

Additional info:
server doesn't search clients in ldap (I don't see searches in ldap)
Comment 1 Nikolai Kondrashov 2014-12-04 08:28:22 UTC 
David, do you have a test which I can use to reproduce this?
Comment 8 Jaroslav Aster 2016-03-09 15:00:12 UTC 
Hi,

I can confirm the bug. File /usr/share/doc/freeradius-3.0.4/schemas/ldap/openldap/freeradius-clients.schema defines objectClass with name radiusClient

objectclass ( 1.3.6.1.4.1.11344.1.100.1.1 
        NAME 'radiusClient' 
        DESC 'radiusClient object class' 
        SUP top 
        STRUCTURAL 
        MUST ( radiusClientIdentifier $ radiusClientSecret ) 
        MAY ( radiusClientShortname $ radiusClientVirtualServer $ radiusClientType $ radiusClientRequireMa $ radiusClientComment ) 
 )

, but there is a filter for clients in /etc/raddb/mods-available/ldap which searches objectClass frClient.

#
#  Filter to match client objects
#
filter = '(objectClass=frClient)'

For administrator, it is easy to change the filter, but I think, we should keep it consistent. Fix is easy, change filter to

filter = '(objectClass=radiusClient)'
Comment 10 Nikolai Kondrashov 2016-04-19 10:43:45 UTC 
Thanks for the investigation, Jaroslav, you saved me a great deal of time :)
I found that the new version has this fixed.
Comment 12 Nikolai Kondrashov 2017-02-15 16:47:17 UTC 
This can be fixed with a rebase to 3.0.12.
Comment 16 errata-xmlrpc 2017-08-01 20:36:03 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://access.redhat.com/errata/RHEA-2017:1954
Note You need to log in before you can comment on or make changes to this bug.