Bug 1663566 - [RGW-LDAP]: segfault in ExternalAuthStrategy constructor when no LDAP secret file configured
Summary: [RGW-LDAP]: segfault in ExternalAuthStrategy constructor when no LDAP secret ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: RGW
Version: 3.2
Hardware: All
OS: All
low
low
Target Milestone: z1
: 3.2
Assignee: Matt Benjamin (redhat)
QA Contact: Tejas
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-04 21:42 UTC by Matt Benjamin (redhat)
Modified: 2019-03-07 15:51 UTC (History)
8 users (show)

Fixed In Version: RHEL: ceph-12.2.8-76.el7cp Ubuntu: ceph_12.2.8-61redhat1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-07 15:51:27 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Ceph Project Bug Tracker 24228 0 None None None 2019-01-04 21:42:56 UTC
Red Hat Product Errata RHBA-2019:0475 0 None None None 2019-03-07 15:51:36 UTC

Description Matt Benjamin (redhat) 2019-01-04 21:42:56 UTC
Description of problem (from Ceph tracker issues):

"""
The default configuration for rgw_ldap_secret seems to be set to /etc/openldap/secret, which on my system is empty:

    ceph-conf -D | grep ldap
    rgw_ldap_binddn = uid=admin,cn=users,dc=example,dc=com
    rgw_ldap_dnattr = uid
    rgw_ldap_searchdn = cn=users,cn=accounts,dc=example,dc=com
    rgw_ldap_searchfilter =
    rgw_ldap_secret = /etc/openldap/secret
    rgw_ldap_uri = ldaps://<ldap.your.domain>
    rgw_s3_auth_use_ldap = false

    cat /etc/openldap/secret
    cat: /etc/openldap/secret: No such file or directory

The code assumes that if it is set, the named file has content. Since it doesn’t, safe_read_file() asserts.

I set it to nothing (rgw_ldap_secret = ) in my configuration, and everything seems happy.
"""

Comment 10 errata-xmlrpc 2019-03-07 15:51:27 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/RHBA-2019:0475


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