Hi Ondrej,
thank you for your answer.
Am 02.04.24 um 10:47 schrieb Ondřej Kuzník:
I assume libsasl2 is linked to heimdal, which doesn't (yet?) support
KCM? And on Debian you might have been using heimdal as your libkrb5, so
no KCM cache used.
Then that's strange because I only installed redhat-p
On Mon, Apr 01, 2024 at 03:09:12PM +0200, Stefan Kania wrote:
> I normally use Debian for OpenLDAP and Kerberos, but now I have to uses
> Alamalinux 9. When I create a Ticket with kinit I'm getting:
> -
> u1-prod@ldapserver1 ~]$ kinit
> Password for u1-p...@example.net:
> [u1-prod@ldapserve
Am 01.04.24 um 17:02 schrieb Stefan Kania:
As soon as I change to KCM: it's not working anymore :-. That's why I
was thinking that there is maybe some settings for the openldap-client
commands
I'm not aware of such an configuration setting.
Only idea is a wrong setting of $KRB5CCNAME, but I
Hello Ulf,
thank you for your fast answer even on Easter Monday :-)
Am 01.04.24 um 16:48 schrieb Ulf Volmer:
/etc/krb5.conf.d/kcm_default_ccache is your friend.
That's what I changed to go back to FILE: but I can't get ldapsearch and
ldapwhoami working with KCM:
I did not changed anything
Am 01.04.24 um 15:09 schrieb Stefan Kania:
I normally use Debian for OpenLDAP and Kerberos, but now I have to
uses Alamalinux 9. When I create a Ticket with kinit I'm getting:
-
u1-prod@ldapserver1 ~]$ kinit
Password for u1-p...@example.net:
[u1-prod@ldapserver1 ~]$ klist
Ticket cache:
I normally use Debian for OpenLDAP and Kerberos, but now I have to uses
Alamalinux 9. When I create a Ticket with kinit I'm getting:
-
u1-prod@ldapserver1 ~]$ kinit
Password for u1-p...@example.net:
[u1-prod@ldapserver1 ~]$ klist
Ticket cache: KCM:10001
Default principal: u1-p...@example.