Subject: How about Softerra ldapbrowser?
Author: eLDAP
In response to: You cannot reach a Kerberized service with the IP Address
Posted on: 10/18/2013 10:46:58 PM
Softerra is underlyingly using same library as LDP.exe. The error cases are the same. Only difference is the UI presentation:
Other Credentials:
Mechanism: GSS Negotiate
Principal: <principal>
Password: <passoword>
where there is only one line for
User and
Domain information, called
Principal. Thereafter,
If you want Kerberos authentication, you must type in:
Principal:
testuser@MYCOMPANY.COMotherwise, anything like
Principal:
MYCOMPANY\testuseror
Principal:
testuserwill trigger the backup unsecured NTLM authentication protocol.
>
> On 07/02/2010 08:44:17 PM
eLDAP wrote:
The server host name must be a FQDN. If you just provide a netBIOS name, the Kerberos protocol will not go through either.
Server: myAD
Port: 389
Bind Function Type: Generic
Bind method: SSPI
Synchronous: checked
Use auth. identit: checked
User: testuser
Password: <password>
(box checked)Domain: MYCOMPANY.COM
You will get, on the client side, the following:
res = ldap_bind_s(ld, NULL, &NtAuthIdentity, 1158); // v.3
{NtAuthIdentity: User='testuser'; Pwd= <unavailable>; domain = 'MYCOMPANY.COM'.}
Authenticated as dn:'testuser'.
On the server side, binding request was received but it used NTLM for SASL GSS-SPNEGO instead.
References: