openldap-technical

openldap-technical@openldap.org

9 participants
9868 discussions

Re: ldapsearch not working with '-H ldap://<IP_LDAP_server>/' option
by Thierry Debaene 12 Mar '20

12 Mar '20

Dear Quanah, Herewith the requested info. Thanks a lot for you help and time ! Kind Regards, Thierry client# ldapwhoami -x -H ldap://192.168.100.11/ -D "cn=Manager,dc=be" -w password -d 1 ldap_url_parse_ext(ldap://192.168.100.11/) ldap_create ldap_url_parse_ext(ldap://192.168.100.11:389/??base) ldap_sasl_bind ldap_send_initial_request ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP 192.168.100.11:389 ldap_new_socket: 3 ldap_prepare_socket: 3 ldap_connect_to_host: Trying 192.168.100.11:389 ldap_pvt_connect: fd: 3 tm: -1 async: 0 attempting to connect: connect success ldap_open_defconn: successful ldap_send_server_request ber_scanf fmt ({it) ber: ber_scanf fmt ({i) ber: ber_flush2: 38 bytes to sd 3 ldap_result ld 0x55d49a4a3070 msgid 1 wait4msg ld 0x55d49a4a3070 msgid 1 (infinite timeout) wait4msg continue ld 0x55d49a4a3070 msgid 1 all 1 ** ld 0x55d49a4a3070 Connections: * host: 192.168.100.11 port: 389 (default) refcnt: 2 status: Connected last used: Wed Mar 11 20:32:08 2020 ** ld 0x55d49a4a3070 Outstanding Requests: * msgid 1, origid 1, status InProgress outstanding referrals 0, parent count 0 ld 0x55d49a4a3070 request count 1 (abandoned 0) ** ld 0x55d49a4a3070 Response Queue: Empty ld 0x55d49a4a3070 response count 0 ldap_chkResponseList ld 0x55d49a4a3070 msgid 1 all 1 ldap_chkResponseList returns ld 0x55d49a4a3070 NULL ldap_int_select read1msg: ld 0x55d49a4a3070 msgid 1 all 1 ber_get_next ldap_err2string ldap_result: Can't contact LDAP server (-1) ldap_free_request (origid 1, msgid 1) ldap_free_connection 1 1 ldap_free_connection: actually freed server# ldapwhoami -x -D "uid=thierry,ou=People,ou=linux,dc=be" -w password -d 1 ldap_create ldap_sasl_bind ldap_send_initial_request ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP localhost:389 ldap_new_socket: 3 ldap_prepare_socket: 3 ldap_connect_to_host: Trying ::1 389 ldap_pvt_connect: fd: 3 tm: -1 async: 0 attempting to connect: connect success ldap_open_defconn: successful ldap_send_server_request ber_scanf fmt ({it) ber: ber_scanf fmt ({i) ber: ber_flush2: 58 bytes to sd 3 ldap_result ld 0x563d667e3060 msgid 1 wait4msg ld 0x563d667e3060 msgid 1 (infinite timeout) wait4msg continue ld 0x563d667e3060 msgid 1 all 1 ** ld 0x563d667e3060 Connections: * host: localhost port: 389 (default) refcnt: 2 status: Connected last used: Wed Mar 11 20:30:44 2020 ** ld 0x563d667e3060 Outstanding Requests: * msgid 1, origid 1, status InProgress outstanding referrals 0, parent count 0 ld 0x563d667e3060 request count 1 (abandoned 0) ** ld 0x563d667e3060 Response Queue: Empty ld 0x563d667e3060 response count 0 ldap_chkResponseList ld 0x563d667e3060 msgid 1 all 1 ldap_chkResponseList returns ld 0x563d667e3060 NULL ldap_int_select read1msg: ld 0x563d667e3060 msgid 1 all 1 ber_get_next ber_get_next: tag 0x30 len 12 contents: read1msg: ld 0x563d667e3060 msgid 1 message type bind ber_scanf fmt ({eAA) ber: read1msg: ld 0x563d667e3060 0 new referrals read1msg: mark request completed, ld 0x563d667e3060 msgid 1 request done: ld 0x563d667e3060 msgid 1 res_errno: 0, res_error: <>, res_matched: <> ldap_free_request (origid 1, msgid 1) ldap_parse_result ber_scanf fmt ({iAA) ber: ber_scanf fmt (}) ber: ldap_msgfree ldap_extended_operation ldap_send_initial_request ldap_send_server_request ber_scanf fmt ({it) ber: ber_scanf fmt ({) ber: ber_flush2: 32 bytes to sd 3 ldap_result ld 0x563d667e3060 msgid -1 wait4msg ld 0x563d667e3060 msgid -1 (timeout 100000 usec) wait4msg continue ld 0x563d667e3060 msgid -1 all 1 ** ld 0x563d667e3060 Connections: * host: localhost port: 389 (default) refcnt: 2 status: Connected last used: Wed Mar 11 20:30:44 2020 ** ld 0x563d667e3060 Outstanding Requests: * msgid 2, origid 2, status InProgress outstanding referrals 0, parent count 0 ld 0x563d667e3060 request count 1 (abandoned 0) ** ld 0x563d667e3060 Response Queue: Empty ld 0x563d667e3060 response count 0 ldap_chkResponseList ld 0x563d667e3060 msgid -1 all 1 ldap_chkResponseList returns ld 0x563d667e3060 NULL ldap_int_select read1msg: ld 0x563d667e3060 msgid -1 all 1 ber_get_next ber_get_next: tag 0x30 len 53 contents: read1msg: ld 0x563d667e3060 msgid 2 message type extended-result ber_scanf fmt ({eAA) ber: read1msg: ld 0x563d667e3060 0 new referrals read1msg: mark request completed, ld 0x563d667e3060 msgid 2 request done: ld 0x563d667e3060 msgid 2 res_errno: 0, res_error: <>, res_matched: <> ldap_free_request (origid 2, msgid 2) ldap_parse_result ber_scanf fmt ({iAA) ber: ber_scanf fmt (x) ber: ber_scanf fmt (}) ber: ldap_parse_extended_result ber_scanf fmt ({eAA) ber: ber_scanf fmt (O) ber: dn:uid=thierry,ou=People,ou=linux,dc=be ldap_msgfree ldap_free_connection 1 1 ldap_send_unbind ber_flush2: 7 bytes to sd 3 ldap_free_connection: actually freed Op wo 11 mrt. 2020 om 18:15 schreef Quanah Gibson-Mount <quanah(a)symas.com>: > > > --On Wednesday, March 11, 2020 10:08 AM +0100 Thierry Debaene > <thierry.debaene(a)gmail.com> wrote: > > > > > > > Dear Quanah, OpenLDAPs, > > > > > > Herewith the proof that slapd is listening on port 389. > > I also included the slapd.conf, /etc/sysconfig/slapd and ldap.conf files. > > I would: > > a) Start with ldapwhoami (rather than ldapsearch), just for simplicity > b) add a -d -1 for full client side debugging to see where it's getting > hung up > > --Quanah > > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

2 2

Information about source code of mobiuniquemember
by HANCHATE Ravikiran (u5574292) 11 Mar '20

11 Mar '20

Dear, we need information about source code of mobiuniquemember. How can we find source code of mobiuniquemember for our Opneldap infra ? Kindly assist here . Regards, Ravikiran. *********DISCLAIMER********* This electronic transmission (and any attached document) is intended exclusively for the person or entity to whom it is addressed and may contain confidential and/or privileged material. Any disclosure, copying, distribution or other action based upon the information by persons or entities other than the intended recipient is prohibited. If you receive this message in error, please contact the sender and delete the material from any and all computers. Orange Belgium does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. Unless clearly and unambiguously stated otherwise, the content of this e-mail and its attachment is provided to you for information purposes only, and nothing herein shall be binding upon, or shall constitute or be construed as a binding offer of Orange Belgium. *****END OF DISCLAIMER*****

2 1

Re: ldapsearch not working with '-H ldap://<IP_LDAP_server>/' option
by Thierry Debaene 11 Mar '20

11 Mar '20

Dear Quanah, OpenLDAPs, Herewith the proof that slapd is listening on port 389. I also included the slapd.conf, /etc/sysconfig/slapd and ldap.conf files. Regards, Thierry # netstat -ltn Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State tcp 0 0 0.0.0.0:389 0.0.0.0:* LISTEN tcp 0 0 127.0.0.1:8080 0.0.0.0:* LISTEN tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN tcp6 0 0 :::389 :::* LISTEN tcp6 0 0 :::3306 :::* LISTEN tcp6 0 0 :::22 :::* LISTEN # nc -zv 192.168.100.11 389 Ncat: Version 7.50 ( https://nmap.org/ncat ) Ncat: Connected to 192.168.100.11:389. Ncat: 0 bytes sent, 0 bytes received in 0.01 seconds. # cat /etc/openldap/slapd.conf include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/ppolicy.schema allow bind_v2 idletimeout 10 pidfile /var/run/openldap/slapd.pid argsfile /var/run/openldap/slapd.args modulepath /usr/lib64/openldap moduleload ppolicy.la moduleload syncprov password-hash {CRYPT} password-crypt-salt-format "$6$%.86s" access to * by * read database bdb suffix "dc=be" rootdn "cn=Manager,dc=be" rootpw {CRYPT}$6$DAn/HuEvv8oxXzht$4...k4ZUiJG4qUKzqUTCQVtuUY1 directory /var/lib/ldap index objectClass eq,pres index ou,cn,mail,surname,givenname eq,pres,sub index uidNumber,gidNumber,loginShell eq,pres index uid,memberUid eq,pres,sub index nisMapName,nisMapEntry eq,pres,sub overlay ppolicy ppolicy_default "cn=default,ou=policies,dc=be" ppolicy_use_lockout # cat /etc/sysconfig/slapd SLAPD_URLS="ldapi:/// ldap:///" # cat /etc/openldap/ldap.conf #TLS_CACERTDIR /etc/openldap/certs #TLS_CACERTDIR /etc/openldap/cacerts TLS_REQCERT never SASL_NOCANON on Op di 10 mrt. 2020 om 19:42 schreef Quanah Gibson-Mount <quanah(a)symas.com>: > --On Tuesday, March 10, 2020 12:03 PM +0100 Thierry Debaene > <thierry.debaene(a)gmail.com> wrote: > > ># ldapsearch -x -H ldap://192.168.100.11 -D > ># "uid=thierry,ou=People,ou=linux,dc=be" -w password -b ou=linux,dc=be > ># -LLL memberUid -v > > ldap_initialize( ldap://192.168.100.11:389/??base ) > > ldap_result: Can't contact LDAP server (-1) > > Please provide evidence that slapd is listening to 192.168.100.11 on port > 389 and that it can be accessed (i.e., no firewall etc blocking access). > > For example on my local system: > > nc -zv 10.2.0.74 389 > Connection to 10.2.0.74 389 port [tcp/ldap] succeeded! > > Regards, > Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

2 1

ldapsearch not working with '-H ldap://<IP_LDAP_server>/' option
by Thierry Debaene 10 Mar '20

10 Mar '20

Hello OpenLDAPs, Any LDAP search request with '-H ldap://<IP_LDAP_server>/' option returns 'Can't contact LDAP server (-1)' (see below). When the '-H ...' option is left out or when '-H ldap:///' is used, the expected result is returned (see below). The 'ldapsearch -x -H ldap://<IP_LDAP_server>/ ...' behaves the same from the server as from a client on the same LAN. Thanks for helping me to get rid of this problem. Thierry # ldapsearch -x -H ldap://192.168.100.11 -D "uid=thierry,ou=People,ou=linux,dc=be" -w password -b ou=linux,dc=be -LLL memberUid -v ldap_initialize( ldap://192.168.100.11:389/??base ) ldap_result: Can't contact LDAP server (-1) # ldapsearch -x -D "uid=thierry,ou=People,ou=linux,dc=be" -w password -b ou=linux,dc=be -LLL memberUid -v ldap_initialize( <DEFAULT> ) filter: (objectclass=*) requesting: memberUid dn: cn=thierry,ou=Group,ou=linux,dc=be memberUid: thierry # ldapsearch -x -H ldap:/// -D "uid=thierry,ou=People,ou=linux,dc=be" -w password -b ou=linux,dc=be -LLL memberUid -v ldap_initialize( ldap://:389/??base ) filter: (objectclass=*) requesting: memberUid memberUid: thierry

2 1

Re: back-ldap SASL proxy authorization
by Dieter Bocklandt 09 Mar '20

09 Mar '20

Hi Quanah, Of course! Submitted this as ITS#9179. Regards, //Dieter On Fri, 6 Mar 2020 at 17:52, Quanah Gibson-Mount <quanah(a)symas.com> wrote: > > > --On Thursday, March 5, 2020 8:04 PM +0000 Howard Chu <hyc(a)symas.com> > wrote: > > >> Actually, I spent some more time on this today and I /think/ I might > >> know what's happening here: > > > > Your analysis makes sense. Would have to ask Pierangelo why he wrote it > > the way he did but it seems that it should use op->o_ndn. > > Hi Dieter, > > Can you file an ITS on this issue at http://www.openldap.org/its > including > your analysis? > > Thanks! > > Regards, > Quanah > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

1 0

Memory mapping questions
by Sam Dave 09 Mar '20

09 Mar '20

Hi, 1. Is it possible to disable memory mapping in LMDB? 2. If I create a brand-new database and write data into it (but haven't read it yet) can I be assured it won't be memory-mapped yet? The purpose of these question is to get more consistent/reproducible time benchmarks for some stuff I'm doing. (As you know the drive vs. memory-mapped performance varies heavily.) Thanks, Sam

3 3

Re: back-ldap SASL proxy authorization
by Dieter Bocklandt 06 Mar '20

06 Mar '20

Hey Quanah, Thanks for getting back to me! So as I understood it, I expected the proxied identity to be the identity that the client successfully authorized as instead of the identity it initially started with. The session tracking request is just there to confirm that piece of information is actually present but not used. That initial identity is also used for ACL evaluation on the producer side, leading to insufficient access (as expected). To give a maybe more clear example, assume the following users (stripped down to just the relevant attributes in play): *dn: cn=proxy,ou=System,dc=example,dc=netauthzTo: dn:** *dn: cn=service,ou=System,dc=example,dc=net * *authzTo: dn:uid=user,ou=People,dc=example,dc=net * *dn: uid=dieter,ou=People,dc=example,dc=net * *and the following idassert config:* *olcDbIDAssertBind: mode=self flags=override,prescriptive tls_reqcert=never bindmethod=sasl saslmech=plain authcID=proxy credentials=XXXXX * When I perform an operation like this: ldapmodify -H ldaps://ldapserver -Y PLAIN -U service -X dn:uid=dieter,ou=People,dc=example,dc=net -w servicepassword -f modifications.ldif I would assume the following takes place: - The service user binds to the consumer and assumes dieter's identity, which should be the same net effect as binding with dieter's user in the first place. - The proxy user binds to the provider and assumes dieter's identity - The provider tries to perform the write, using dieter's identity for ACL evaluation What actually happens: - The service user binds to the consumer and assumes dieter's identity - The proxy user binds to the provider and assumes the service user's identity - The provider tries to perform the write, using the service user's identity for ACL evaluation Actually, I spent some more time on this today and I *think* I might know what's happening here: (from servers/slapd/back-ldap/bind.c in master): line 2222 - 2227: *if ( !BER_BVISNULL( &op->o_conn->c_ndn ) ) { ndn = op->o_conn->c_ndn; } else { ndn = op->o_ndn; }* line 2549 - 2557: *if ( op->o_tag == LDAP_REQ_BIND ) { ndn = op->o_req_ndn; } else if ( !BER_BVISNULL( &op->o_conn->c_ndn ) ) { ndn = op->o_conn->c_ndn; } else { ndn = op->o_ndn; }* It seems it tries to use op->o_conn->c_ndn if it's not null, which is (correct me if I'm wrong) the original authcID. That value however doesn't change when performing a proxy authorization, while op->o_ndn does properly reflect that. Shouldn't OpenLDAP always use op->o_ndn? Again, let me know if I can provide more information or tell me if I'm grossly misunderstanding how this is all supposed to work in the first place :) Thanks! // Dieter On Wed, 4 Mar 2020 at 23:12, Quanah Gibson-Mount <quanah(a)symas.com> wrote: > > > --On Friday, February 28, 2020 11:11 PM +0100 Dieter Bocklandt > <dieterbocklandt(a)gmail.com> wrote: > > > However, we also have a service using SASL proxy authorization, in which > > case the authcid is used in the ProxyAuthz instead of the authorized > > authzid. > > > > Feb 28 22:02:38 ldap-master-az2 slapd[1915]: conn=26858 op=2 PROXYAUTHZ > > dn="cn=service,ou=system,dc=internal,dc=machines" > > Feb 28 22:02:38 ldap-master-az2 slapd[1915]: conn=26858 op=2 > > [IP=10.243.72.199 USERNAME=cn=enduser,ou=People,dc=example,dc=net] MOD > > dn="uid=sys.cp.test,ou=People,dc=internal,dc=machines" > > > > Am I misunderstanding how this is supposed to work, am I hitting a > > certain limitation or maybe a bug? Let me know if you need any more > > details! > > This looks to me like it: > > a) Logs what the proxied identity is (PROXYAUTHZ > dn="cn=service,ou=system,dc=internal,dc=machine") > > b) Logs what the actual identity making the changes is > (USERNAME=cn=enduser,ou=People,dc=example,dc=net) and what IP address it > came from (IP=10.243.72.199) so that if questions arise about who made a > change, those questions can be answered from the logs. > > I.e., I see both bits of information provided in the connection operation. > > What makes you think you are hitting a limitation or a bug? > > Regards, > Quanah > > > -- > > Quanah Gibson-Mount > Product Architect > Symas Corporation > Packaged, certified, and supported LDAP solutions powered by OpenLDAP: > <http://www.symas.com> >

4 3

Re: openldap-technical Digest, Vol 148, Issue 6
by Dieter Bocklandt 06 Mar '20

06 Mar '20

Hey Michael, I would assume that for the proxy it shouldn't matter how the client got authenticated to the consumer. Mode=self should just try and assert the resulting authzID to the target. The identity of the proxy is only there so we have something to bind with to the producer. With mode=none, that identity would also be used for the actual ACL evaluation, but that would just lead to all writes being done by seemingly 1 user, making auditing impossible ... Cheers, //Dieter On Fri, 6 Mar 2020 at 13:00, <openldap-technical-request(a)openldap.org> wrote: > > ---------- Forwarded message ---------- > From: "Michael Ströder" <michael(a)stroeder.com> > To: openldap-technical(a)openldap.org > Cc: > Bcc: > Date: Thu, 5 Mar 2020 21:46:12 +0100 > Subject: Re: back-ldap SASL proxy authorization > On 3/5/20 9:04 PM, Howard Chu wrote: > > Dieter Bocklandt wrote: > >> I would assume the following takes place: > >> - The service user binds to the consumer and assumes dieter's identity, > which should be the same net effect as binding with dieter's user in the > first place. > >> - The proxy user binds to the provider and assumes dieter's identity > >> - The provider tries to perform the write, using dieter's identity for > ACL evaluation > >> > >> What actually happens: > >> - The service user binds to the consumer and assumes dieter's identity > >> - The proxy user binds to the provider and assumes the service user's > identity > >> - The provider tries to perform the write, using the service user's > identity for ACL evaluation > >> > >> Actually, I spent some more time on this today and I /think/ I might > know what's happening here: > > > > Your analysis makes sense. Would have to ask Pierangelo why he wrote it > the way he > > did but it seems that it should use op->o_ndn. > > Hmm, is the semantics of proxying the SASL proxy authorization clearly > defined? The consumer proxy itself also has an identity. > > Just asking... > > Ciao, Michael. > > > _______________________________________________ > openldap-technical mailing list > openldap-technical(a)openldap.org > http://www.openldap.org/lists/mm/listinfo/openldap-technical >

1 0

Antw: [EXT] Re: pwdChangedTime not defined when creating new entry
by Ulrich Windl 05 Mar '20

05 Mar '20

>>> Dieter Klünter <dieter(a)dkluenter.de> schrieb am 05.03.2020 um 10:10 in Nachricht <25580_1583399661_5E60C2EC_25580_1796_1_20200305101027.4c15a1d1(a)pink.fritz.box>: > Am Wed, 04 Mar 2020 13:36:08 +0000 > schrieb Manuela Mandache <manuela.mandache(a)protonmail.com>: > >> Hello all, >> >> We have a directory running on OpenLDAP 2.4.44 with the ppolicy >> overlay on the main database. When a new entry with a userPassword >> defined is created, pwdChangedTime is not defined, so this initial >> userPassword never expires. >> >> The directory has been migrated from its OpenLDAP 2.3.34 instance >> (yes, we missed some steps...), and there the pwdChangedTime is set, >> and naturally equal to createTimestamp. >> >> The overlay is configured as follows: >> dn: olcOverlay={2}ppolicy,olcDatabase={2}mdb,cn=config >> objectClass: olcOverlayConfig >> objectClass: olcPPolicyConfig >> olcOverlay: {2}ppolicy >> olcPPolicyDefault: ou=ppolicy,dc=example,dc=com >> olcPPolicyHashCleartext: TRUE >> olcPPolicyUseLockout: TRUE >> >> Is there a parameter I missed which would switch on setting >> pwdChangedTime at entry creation? Do I have to provide some other >> configuration elements? >> >> Or is it unreasonable to expect this initialisation of the attribute >> this way, and only a password change can set it? I think the setting >> at creation is rather handy... Using pwdMustChange would be >> difficult, we have a lot of client apps which would be forced to >> check and probably adapt their authentication procedures. > [...] > The password attribute value must be set by a password modify exented > operation in order to set password policy in effect, see man > slapo-ppolicy(5) Yes, but shouldn't there be some magic to add it to all existing passweords when enabling it? Without having each user to change the password... > > -Dieter > > -- > Dieter Klünter | Systemberatung > http://sys4.de > GPG Key ID: E9ED159B > 53°37'09,95"N > 10°08'02,42"E

2 1

back-ldap SASL proxy authorization
by Dieter Bocklandt 04 Mar '20

04 Mar '20

Hi! We have a fairly standard OpenLDAP setup (on 2.4.49) running well, where our replica instances chain writes back to the master using the chain overlay. Relevant bits of configuration we're using below: dn: olcOverlay={0}chain,olcDatabase={-1}frontend,cn=config objectClass: olcOverlayConfig objectClass: olcChainConfig olcOverlay: {0}chain olcChainCacheURI: FALSE olcChainMaxReferralDepth: 1 olcChainReturnError: TRUE dn: olcDatabase={0}ldap,olcOverlay={0}chain,olcDatabase={-1}frontend,cn=config objectClass: olcLDAPConfig objectClass: olcChainDatabase olcDatabase: {0}ldap olcDbIDAssertBind: mode=self flags=override,prescriptive tls_reqcert=never bindmethod=sasl saslmech=plain authcID=proxy credentials=XXXXX olcDbRebindAsUser: TRUE olcDbChaseReferrals: TRUE olcDbProxyWhoAmI: TRUE olcDbProtocolVersion: 3 olcDbSingleConn: FALSE olcDbCancel: abandon olcDbUseTemporaryConn: FALSE olcDbConnectionPoolMax: 8 olcDbSessionTrackingRequest: TRUE olcDbNoRefs: FALSE olcDbNoUndefFilter: FALSE olcDbIdleTimeout: 5 . . . dn: cn=proxy,ou=System,dc=example,dc=net cn: proxy objectClass: simpleSecurityObject objectClass: organizationalRole userPassword: XXXXX authzTo: {0}dn.regex:^uid=[^,],ou=People,dc=example,dc=net$ Above works great, with the client identity being authorized through the ProxyAuthz control. However, we also have a service using SASL proxy authorization, in which case the authcid is used in the ProxyAuthz instead of the authorized authzid. Ldapwhoami works as expected and the username mentioned in the session tracking request (visible in the producer's logs) is actually the authzdn (being cn=enduser,ou=People,dc=example,dc=net in this example, whereas cn=service,ou=system,dc=internal,dc=machines is the authcdn): ldapwhoami -H ldaps://$(cat /etc/service_hostname) -U service -X dn:cn=enduser,ou=People,dc=example,dc=net -Y PLAIN SASL/PLAIN authentication started Please enter your password: SASL username: dn:cn=enduser,ou=People,dc=example,dc=net SASL SSF: 0 dn:cn=enduser,ou=People,dc=example,dc=net Feb 28 22:02:38 ldap-master-az2 slapd[1915]: conn=26858 op=2 PROXYAUTHZ dn="cn=service,ou=system,dc=internal,dc=machines" Feb 28 22:02:38 ldap-master-az2 slapd[1915]: conn=26858 op=2 [IP=10.243.72.199 USERNAME=cn=enduser,ou=People,dc=example,dc=net] MOD dn="uid=sys.cp.test,ou=People,dc=internal,dc=machines" Feb 28 22:02:38 ldap-master-az2 slapd[1915]: conn=26858 op=2 [IP=10.243.72.199 USERNAME=cn=enduser,ou=People,dc=example,dc=net] MOD attr=klarnaItNote Feb 28 22:02:38 ldap-master-az2 slapd[1915]: conn=26858 op=2 [IP=10.243.72.199 USERNAME=cn=enduser,ou=People,dc=example,dc=net] RESULT tag=103 err=0 text= Am I misunderstanding how this is supposed to work, am I hitting a certain limitation or maybe a bug? Let me know if you need any more details! Thanks! Dieter Bocklandt

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical