really bug in slurpd?

[Tarassov Vadim <Vadim.Tarassov@winterthur.ch>]

Hallo again,

Does anyone know what could be authcId when using EXTERNAL SASL mechanism?
Problem is that slurpd expects due to

#ifdef NEW_LOGGING
        LDAP_LOG (( "operation", LDAP_LEVEL_ARGS,
                "do_bind: bind to %s as %s via %s (SASL)\n",
                ri->ri_hostname, ri->ri_authcId, ri->ri_saslmech ));
#else
        Debug( LDAP_DEBUG_ARGS, "bind to %s as %s via %s (SASL)\n",
                ri->ri_hostname, ri->ri_authcId, ri->ri_saslmech );
#endif

in ldap_op.c

authcId in slapd.conf, otherwise it crashes. I can imagine what authcid could be in case of CRAM-MD5, for example, but what if I want to use EXTERNAL?

Anyway, defining something senseless as authcid and using EXTERNAL as saslmech in slurpd does not help, because TLS handshake does not work between slapd and slurpd:

TLS: error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did not return a certificate s3_srvr.c:1788

Am I doing wrong something?

Regards, Vadim Tarassov.

-----Ursprüngliche Nachricht-----
Von: vadim tarassov [mailto:vadim.tarassov@swissonline.ch]
Gesendet am: Donnerstag, 20. Juni 2002 23:05
An: openldap-software@OpenLDAP.org
Betreff: bug in slurpd?

Hallo everybody,

I would like to inform you that my slurpd dumps on Solaris 2.6 if I want 
him to authenticate with slave ldap via SASL. Last thing which he wrote 
was "ldap_create". I will try to rebuild everything with debug 
information and look in core dump, but if someone knows what's wrong 
please share this knowledge with me!

Regards, Vadim Tarassov.