Supposedly, $KRB5CCNAME is set. So the problem seems to be
that cifs.upcall is not looking at this value. Perhaps this
is because systemd.automount is doing things as root?
In any case, cifs.upcall is not getting the information it needs
to work properly. If the cause is that the automounting is
happening as root, I don't see that there's a mechanism in place
whereby it could. At least not by adding fstab entries. Perhaps
there's some systemd-fu that would make it work.
Regards,
Karl <email address hidden>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
Hi,
FYI. Looks like the "extra stuff" added to the credential
cache name comes from sssd, via pam_sss, or perhaps pam_sss_gss.
Further information here:
https:/ /bugs.debian. org/cgi- bin/bugreport. cgi?bug= 1033164
Supposedly, $KRB5CCNAME is set. So the problem seems to be
that cifs.upcall is not looking at this value. Perhaps this
is because systemd.automount is doing things as root?
In any case, cifs.upcall is not getting the information it needs
to work properly. If the cause is that the automounting is
happening as root, I don't see that there's a mechanism in place
whereby it could. At least not by adding fstab entries. Perhaps
there's some systemd-fu that would make it work.
Regards,
Karl <email address hidden>
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein