Re: Usage of the machine account for ldapsearch
Rowland Penny via samba <[email protected]> Mon, 16 Feb 2026 15:55:34 +0000
| Newsgroups | gmane.network.samba.general |
|---|---|
| Message-ID | <[email protected]> |
On Mon, 16 Feb 2026 08:07:46 +0100 Matthias Kühne | Ellerhold Aktiengesellschaft via samba <[email protected]> wrote: > Hello Christian, > > Thanks! Ive got the Keytab now and klist -kte /etc/krb5.keytab shows > entries, but using kinit on them leads to an error: > > kinit -kt /etc/krb5.keytab 'host/[email protected]' > kinit: Client 'host/[email protected]' not found in Kerberos > database while getting initial credentials > > Using kinit with '[email protected]' works though, but the > ldapsearch doesnt work: You shouldn't need to run kinit, the 'machine ticket' is in memory. > > ldapsearch -Q -o ldif-wrap=no -Y GSSAPI -H > ldaps://dc1.ad.ellerhold.lan -b dc=AD,DC=ELLERHOLD,DC=LAN > ldap_sasl_interactive_bind: Invalid credentials (49) > additional info: 80090346: LdapErr: DSID-0C090711, comment: > AcceptSecurityContext error, data 35b, v1db1 > > Any idea what Im doing wrong? Not entirely sure, I tested this against one of my Samba DCs: sudo ldapsearch -Q -o ldif-wrap=no -Y GSSAPI -H ldap://dc01.samdom.example.com -b dc=SAMDOM,DC=EXAMPLE,DC=COM NOTE: I added 'ldap server require strong auth = no' to the DC, to take ldaps out of the picture. I ran the above command and got a dump of my AD domain. I didn't kinit as the computer, winbind does this for you and, as I said, it puts the kerberos ticket in memory. Rowland -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba