mechanism not supported error calling sasl_client_start()

Dan White dwhite at olp.net
Thu Mar 9 12:41:28 EST 2017


On 03/09/17 11:39 -0600, Dan White wrote:
>On 03/09/17 09:24 -0800, Ted Yu wrote:
>>Mar  9 17:08:41 ed19f36081f3 client-test: GSSAPI Error: Unspecified GSS
>>failure.  Minor code may provide more information (No Kerberos credentials
>>available)
>>
>>More background:
>>I am debugging code using docker VM running on Mac, trying to connect to
>>secure server running on:
>>
>>CentOS Linux release 7.2.1511 (Core)
>>
>>If you can give some suggestion on how the user in docker can be
>>authenticated thru Kerberos, that would be nice.
>>
>>Thanks
>
>For most, there's a steep learning curve to getting Kerberos up and going.
>You will need a Kerberos Domain Controller configured and tested prior to
>attempting to get GSSAPI working. I recommend reading through this:
>
>https://web.mit.edu/kerberos/
>
>In short, on the client you'll need to initialize your ticket cache with
>kinit or a similar tool and use klist to verify and view your ticket cache.

This advice is based on the assumption that you actually want to use
GSSAPI. If not, specify DIGEST-MD5 or your preferred mechanism in your
code.

-- 
Dan White


More information about the Cyrus-sasl mailing list