Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The digest-uri does not match any LDAP SPN's registered for this server #160

Open
alexavator opened this issue Mar 16, 2022 · 3 comments
Open
Labels

Comments

@alexavator
Copy link

Describe the bug
I got an error
The digest-uri does not match any LDAP SPN's registered for this server data 0, v4563. Result: 49. Method: BindSasl when I pass just username to Bind method
OR
DSID-0C09058A, comment: AcceptSecurityContext error, data 52e, v4563. Result: 49. Method: BindSasl when I pass usermane@domain to Bind method.

To Reproduce
const int ldapDomainAddressPort = 389;

var ldapConnection = new LdapConnection();
ldapConnection.Connect(domainName.ToLowerInvariant(), ldapDomainAddressPort);
var ldapCredential = new LdapCredential { UserName = userName, Password = plainPassword };
ldapConnection.Bind(Native.LdapAuthType.Digest, ldapCredential);
return ldapConnection;

Expected behavior
I expect successfull connection to AD.

Desktop (please complete the following information):

  • OS: CentOS 7.9. On Windows the same code works well when I use username@domain. On Ubuntu 18.04 the same code works well when I use just username. But when I use username@domain I got the same error as on CentOS.
  • Library version 2.7.2. With newest versions I got an error "libldap.so.2 could not be found" on both Ubuntu and Centos.
  • .NET\core\mono version: .Net5
  • LDAP server: Active Directory
@flamencist
Copy link
Owner

Hi! Please try to install appropriate open ldap libs on you computer and try to test ldap-utils before using library.

@alexavator
Copy link
Author

Hi, @flamencist

I have installed the latest version of openldap-clients package and ldapsearch works correctly.

Also, after several attempts to fix it, I found out the solution - remove SASL_NOCANON parametr from ldap.conf file. But I am not really sure that it is the right solution.

@alexavator
Copy link
Author

hi, is there something about this issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants