Cyrus SASL 2.1.25 / Plugin Testing: GSSAPI

[Info (MateAR.eu)]

Hi.

I'm running sample-server and sample-client in order to test GSSAPI 
plugin. Everything seems to go smoothly till the very end when I get an 
error message. I did google it but I couldn't find any pointer about how 
to fix it.
Find below the full log. I'd appreciate any pointers about how to fix 
this issue.

Thanks in advance.

Sergio.

Test Log
---------

[ Server side ]

Generating client mechanism list...
Sending list of 9 mechanism(s)
S: 
U1JQIEdTU0FQSSBESUdFU1QtTUQ1IE9UUCBDUkFNLU1ENSBOVExNIExPR0lOIFBMQUlOIEFOT05ZTU9VUw==
Waiting for client mechanism...
...
got 'GSSAPI'
Sending response...
S: 
YIGZBgkqhkiG9xIBAgICAG+BiTCBhqADAgEFoQMCAQ+iejB4oAMCARKicQRvmkCNEH6zp+qQphiT8
bYbI8mf+AcS7Mmvo5fzmntnjLTUgnJO5QLvVty6AtB1YRBVSuXCz6FVYMXRyJugdj1B32RcbMSsX3cW1
2gc59USB/jku36HQLfjQR4Po8T9Ih01+bVJAPIw/hFAuzmzcsNV
Waiting for client reply...
...
got ''
Sending response...
S: BQQF/wAMAAwAAAAAMB25dbnieAwen/cmRMX+OQcAAAA=
Waiting for client reply...
...
got '??? '
Negotiation complete
Username: Administrator
Realm: (NULL)
SSF: 56
sending encrypted message 'srv message 1'
S: 
AAAASlRFIFRFTVBPUkFSWSBUQUJMRSBjYWNoZUl0ZXJhdGlvbkUxNTNEMFBpZDE4NTYgQVMgU0VMR
UNUIG5hbWUgRlJPTSBjYWNoZXMA
Waiting for encrypted message...
...


[ Client side ]

recieved 61 byte message
Forcing use of mechanism GSSAPI
Choosing best mechanism from: GSSAPI
returning OK: Administrator
Using mechanism GSSAPI
Preparing initial.
Sending initial response...
C: 
R1NTQVBJAGCCAoIGCSqGSIb3EgECAgEAboICcTCCAm2gAwIBBaEDAgEOogcDBQAgAAAAo4IBUWGCA
U0wggFJoAMCAQWhChsITVkuUkVBTE2iGTAXoAMCAQGhEDAOGwRob3N0GwZsb25kb26jggEZMIIBFaADA
gESoQMCAQGiggEHBIIBAzBMyCx0TFTK8uecvhxcTem5pogtSCdnipr99IdQ254a2ShcR1fXIVQCscuMb
D3SmK0m2WRvGHabWTOFQnEZeqah3mVKBlXLJfLP59NG5ln1d35I/3oABvVKCTDJKZLOG2KDuN9axjidi
ImaAcQxy1bo6WNZ7cjpeXeMf+T/HY5qKi8pbN6cXfAHmLrDULHd+HXAeqWFExj4ly59VRBg6FBhwXw+4
sWnwBTK0xc0v0+3eZL5wg/hjXQbm7LY2PynrRN9QMYMk+6U0xEsUQnWCL82NaUKdGLiHxTJjQa9mGRAd
Fn+RsQ5w34ssJePU+LNn1oNOrxsb4+rbbnb9bbjDQO888SkggEBMIH+oAMCARKigfYEgfPLEd0guaJCn
AL5/f8FtKtp77lNu+DkcYbbku381ZmxV3kkaNk2FCaLGwlCwjK+gUlqXzPTsikRYNYBXwhNog4+/hjR1
dYAWmLAlXsYg64ENvJETwcZdGhau57Ad5W7JOlarxdIoG1D3qtnGE7ZKlndujCFHitp58ENuiQVa3Gcz
01i/2g1xGGNVL/yaa5ZPwunb4kzj1L1Ro8LQ/wtJUV4YXBByM+41VEKY2jf0sPd3kpwmfLz7NlQHWkAO
ALQHuVYMGYJvFoLSZATqUa9J0UWMDOoZRuj3E2onhSNGb6KK71zDWyTaNuDSco3OUxF6cQG/qs=
Waiting for server reply...
...
C:
...
recieved 32 byte message
Sending response...
C: BQQE/wAMAAwAAAAAINYTgW58IqK4fmGTdT98pQQACABBZG1pbmlzdHJhdG9y
Negotiation complete
Username: Administrator
SSF: 56
Waiting for encoded message...
...
recieved 78 byte message
sample-client.exe: SASL Other: GSSAPI Error:  A token was invalid 
(unknown mech-code 0 for mech unknown)
sample-client.exe: sasl_decode: generic failure