Re: Issue with Kerberos authentication using API / MSLSA ccache type

From	Ken Hornstein <kenh@cmf.nrl.navy.mil>
Newsgroups	comp.protocols.kerberos
Subject	Re: Issue with Kerberos authentication using API / MSLSA ccache type
Date	2024-11-23 13:51 -0500
Organization	TNet Consulting
Message-ID	<mailman.141.1732387914.2322.kerberos@mit.edu> (permalink)
References	<CH3PR15MB5514C4E544AC86EFB6D015029B222@CH3PR15MB5514.namprd15.prod.outlook.com> <202411231851.4ANIpgVo016830@hedwig.cmf.nrl.navy.mil>

Show all headers | View raw

>We are using 1.20 Kerberos library on our Windows platform for
>authenticating with our Netezza server.

Are you sure you are using MIT Kerberos?  Because based on the messages
below it sure seems like you actually using the Java Kerberos library
and I was under the impression that was it's own thing.  Also, the
debug messages you show are not ones typically generated by MIT Kerberos.
E.g.:

Java config name: C:\ProgramData\MIT\Kerberos5\krb5.ini
Loading krb5 profile at C:\ProgramData\MIT\Kerberos5\krb5.ini
Loaded from Java config
>>> KdcAccessibility: reset
>>> KdcAccessibility: reset
Acquire TGT from Cache
Principal is MYUSER@NZSQA.IBM.COM
null credentials from Ticket Cache

Nothing I can find in MIT Kerberos generates these messages.  MIT
Kerberos debug messages (which are generated by setting the KRB5_TRACE
environment variable) look like this:

[1613] 1732387726.184428: Response was from primary KDC
[1613] 1732387726.184429: Processing preauth types: PA-ETYPE-INFO2 (19)

--Ken

Back to comp.protocols.kerberos | Previous | Next | Find similar

Thread

Re: Issue with Kerberos authentication using API / MSLSA ccache type Ken Hornstein <kenh@cmf.nrl.navy.mil> - 2024-11-23 13:51 -0500

csiph-web