Welcome to the Centrify Express Forums.
My advice is that you revert the change and troubleshoot the behavior of your appliation to find out the root cause of the issue. Based on your description, sounds like our software was working as expected and sounds like you need to study the interactions of the Kerberos stack and your apps.
The effect that you described (after making the change) are expected. From the configuration and tuning guide: https://docs.centrify.com/en/css/suite2016/centrify-unix-config-guide.pdf (pg 125)
pam.auth.create.krb5.cache
This configuration parameter specifies whether PAM creates the Kerberos user credential cache. A value of true specifies that the Kerberos user credential cache is created. A value of false specifies that the Kerberos user credential cache is not created. The default value is true
For example:
pam.auth.create.krb5.cache: true
Notes
- When this parameter is set to false, the Kerberos user credential cache is not created, and any attempt to perform an SSO operation will fail.
- The Kerberos user credential cache can be file-based or it can be a KCM in-memory cache, depending on the krb5.cache.type setting (see page 111).
- This parameter is also controlled by group policy.
R.P