[Date Prev][Date Next]
Re: passwd extop backend selection (ITS#2851)
- To: email@example.com
- Subject: Re: passwd extop backend selection (ITS#2851)
- From: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
- Date: Mon, 01 Dec 2003 07:40:49 -0800
- Cc: openldap-devel@OpenLDAP.org
- In-reply-to: <200312010647.hB16lipT002637@boole.openldap.org>
- References: <200312010647.hB16lipT002637@boole.openldap.org>
I think this patch should not be applied. (redirected discussion to -devel)
The problem you are trying to solve is internal to slapd(8) and hence shouldn't
be addressed without regard to what's on the wire. That is, the problem here
is purely with slapd(8) management of which backend(s) is associated with the
current LDAP association.
While we could change slapd(8) to support changing of selected (by userIdentity)
passwords, then that's what slapd(8) has to do when a userIdentity is provided.
That is, it must change the password associated with userIdentity. That cannot
be assumed to be the same user as that of the current LDAP association.
At 10:47 PM 11/30/2003, firstname.lastname@example.org wrote:
>Full_Name: Pierangelo Masarati
>OS: Linux RH
>Submission from: (NULL) (18.104.22.168)
>Submitted by: ando
>passwd_extop() in servers/slapd/passwd.c uses op->o_conn->c_authz_backend
>(the authorizing backend) to operate the password change. This patch uses
>the ID field in reqdata, if any, to select the appropriate backend, in
>view of using passwd_extop across backends in glued backend pools.
>Any drawback or security issue?