We have noticed that when folks have Anaconda installed (specifically on Mac, but isn't isolated to Mac if the same thing is happening on other OSs) will override the kerberos credential cache. The CCACHE is set to a KCM: cache instead of the default configured by the system.
anaconda has no business mucking with kerberos configuration and should not be reconfiguring. This is causing user impact to enterprise network services and must be removed.
Actual Behavior
Post install, and configuration of the user's profile, the kerberos ticket cache name is changed to a KCM: based CCACHE. this should never be touched by an application.
Expected Behavior
Anaconda bash profile works as needed for the application without changing system configuration in the user's environment.
Steps to Reproduce
type klist. Note Credential cache location. Install anaconda. reboot, login as user, klist again.
We have noticed that when folks have Anaconda installed (specifically on Mac, but isn't isolated to Mac if the same thing is happening on other OSs) will override the kerberos credential cache. The CCACHE is set to a KCM: cache instead of the default configured by the system.
anaconda has no business mucking with kerberos configuration and should not be reconfiguring. This is causing user impact to enterprise network services and must be removed.
Actual Behavior
Post install, and configuration of the user's profile, the kerberos ticket cache name is changed to a KCM: based CCACHE. this should never be touched by an application.
Expected Behavior
Anaconda bash profile works as needed for the application without changing system configuration in the user's environment.
Steps to Reproduce
type klist. Note Credential cache location. Install anaconda. reboot, login as user, klist again.
Anaconda or Miniconda version:
Anaconda3
Operating System:
MacOS