Ah, this seems to be an issue with MacOS. In MacOS we have "Credentials cache: API:6136D20A-21F8-4FF3-B968-A4415990AFF1" (this is the uuid of a dynamic API that is used to access the ticket cache). When it succeeds (I assume not on MacOS but likely Linux) we have "Ticket cache: FILE:/tmp/krb5cc_26010" which is the expected response for Linux. I am not familiar with how MacOS handles KB5 tickets but it's an interplay between the keychain and your application. There is some interesting information in
https://stackoverflow.com/questions/58653482/what-is-the-default-kerberos-credential-cache-on-osx
which also shows you how to create a Linux type ticket cache.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1981#issuecomment-1486897881", "url": "https://github.com/xrootd/xrootd/issues/1981#issuecomment-1486897881", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1