KRB5CCNAME environment variable is not detected

[Rajesh Kokkonda]

Thanks Greg.  The setting of the environment variables was being done in VS
2022 run time and MIT libraries were using VS2017 run time. Both these run
times were being loaded as part of the process even before the environment
variables were being set. We delayed the loading of the library which was
using VS2017 run time so that environment variables are set first in the
application and then the library is loaded. With this the issue got
resolved.

Thanks,
Rajesh

On Sat, May 18, 2024 at 12:56 AM Greg Hudson <ghudson at mit.edu> wrote:

> On 5/16/24 07:24, Rajesh Kokkonda wrote:
> > We noticed that with the 4.1.0.7 version of the kerberos libraries, the
> > environment variable KRB5CCNAME that is set within the process has no
> > effect.
>
> This sounds like the issue described at
> https://krbdev.mit.edu/rt/Ticket/Display.html?id=2636
> which unfortunately was never resolved--though I don't know specifically
> why two similar versions of the library would exhibit different behavior.
>