kerberos client on windows not being able to access credentials cache ("Internal credentials cache error")

Tomas Pospisek tpo2 at sourcepole.ch
Mon Mar 20 08:28:31 EDT 2023


On 10.03.23 19:25, Ken Hornstein via Kerberos wrote:
>> Also, since I got precisely zilch feedback here while there were other
>> postings here I'm under the impression that this is a mailing list with
>> *no* user support (but instead a development list or similar).
> 
> Dude, I can't speak for anyone else, but I didn't know the answer (and
> it involved Windows, which I am not that familiar with), _and_ my
> day job does not pay me to support people on the MIT Kerberos mailing
> list.  That's not to say I'm opposed to helping people, but if I don't
> know the answer I'm not going to chime in with a "Sorry, I have no idea"
> kind of answer because that doesn't help anyone.

I have to apologize to everyone here and thank you and Sam for your 
feedback: the tone of my original message was an edge to sharp. I should 
have had my frustration under control that my asking a lowly question 
gets no reply on a mailing list with evidently a kiloton of critically 
condensed knowledge in the subject matter. Of course nobody owes me 
nothing here - sorry.

> Judging by the thread you posted, it sure seems like the problem
> was specific to the Postgresql implementation on Windows so it's not
> surprising nobody here would be an expert on that.

The question was in fact not specific to Postgresql. It was pretty much 
a generic "I can't get my windows client to authenticate via 
SSPI/AD/Kerberos". It was just that it was psql that showed the symptoms 
and that I as a newbie in the subject matter was caught up in that 
oekosystem. However the problem is/was a generic client -> 
SSPI/AD/Kerberos one.

Anyway, thanks a lot for pointing out to me what I should do better next 
time!!!

Greetings and thanks to all!
*t



More information about the Kerberos mailing list