Bug 1167846
Summary: | radiusd fails to load clients from ldap | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | David Spurek <dspurek> |
Component: | freeradius | Assignee: | Nikolai Kondrashov <nikolai.kondrashov> |
Status: | CLOSED ERRATA | QA Contact: | Jaroslav Aster <jaster> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | CC: | dpal, jaster, pkis |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-08-01 20:36:03 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1202751 | ||
Bug Blocks: | 1205796 |
Description
David Spurek
2014-11-25 14:07:25 UTC
David, do you have a test which I can use to reproduce this? 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)' Thanks for the investigation, Jaroslav, you saved me a great deal of time :) I found that the new version has this fixed. This can be fixed with a rebase to 3.0.12. 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 |