To clarify if I understand correctly: It is NOT POSSIBLE to use an s3 client like eg. cyberduck/mountainduck and supply a user with an 'Access key' and a 'Password' regardless if the user is defined in ldap or local? I honestly cannot see how this ldap integration should even work, without a proper ldap scheme for auth caps being available. Nor do I understand where you set currently these auth caps, nor do I understand what use the current ldap functionality has. Would be nice to update this on these pages https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html-single/ceph_object_gateway_with_ldapad_guide/index http://docs.ceph.com/docs/master/radosgw/ldap-auth/ Maybe it is good to give some 'beginners' access to the docs pages. Because as they are learning ceph (and maybe missing info in the docs) they can add this then. Because I have the impression that many things asked here could be added to the docs. -----Original Message----- From: Konstantin Shalygin [mailto:k0ste@xxxxxxxx] Sent: zondag 18 maart 2018 5:04 To: ceph-users@xxxxxxxxxxxxxx Cc: Marc Roos; Yehuda Sadeh-Weinraub Subject: Re: Radosgw ldap user authentication issues Hi Marc > looks like no search is being done there. > rgw::auth::s3::AWSAuthStrategy denied with reason=-13 The same for me, http://tracker.ceph.com/issues/23091 But Yehuda closed this. k _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |