mechanism not supported error calling sasl_client_start()
Dan White
dwhite at olp.net
Thu Mar 9 10:15:47 EST 2017
On 03/08/17 15:44 -0800, Ted Yu wrote:
>Hi,
>I installed cyrus-sasl-2.1.26
>
> rc = sasl_client_new(service_name, /* The service we are using*/
> host_name_.c_str(),
> NULL, NULL, /* Local and remote IP address strings
> (NULL disables mechanisms which require this
>info)*/
> NULL, /*connection-specific callbacks*/
> 0 /*security flags*/, &sconn_);
> sasl_security_properties_t *props = new sasl_security_properties_t();
> ::memset(props, 0, sizeof(sasl_security_properties_t));
> props->max_ssf = 2;
> sasl_setprop(sconn_, SASL_SEC_PROPS, (void *)props);
> const char *mechusing, *mechlist = "GSSAPI";
> currentReturnCode = sasl_client_start(sconn_, /* the same context
>from above */
> mechlist, /* the list of mechanisms
> from the server */
> NULL, /* filled in if an
> interaction is needed */
> &out, /* filled in on success */
> &outlen, /* filled in on success */
> &mechusing);
>
>Return value from sasl_client_new() was SASL_OK
>
>The return value from sasl_client_start() was -4.
Use pluginviewer to verify you have the gssapi mechanism available on
the client side. You may want to review the github bug reports for 2.1.26
and GSSAPI:
https://github.com/cyrusimap/cyrus-sasl/issues
Try removing the max_ssf command above until you get past the -4 error.
--
Dan White
More information about the Cyrus-sasl
mailing list