Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-8973: Is the k5login_directory configurable

Centrify DirectControl ,  

21 July,17 at 11:09 PM

Applies to: Centrify Direct Control 2017.1 and above on all supported platforms

Question:
Is it possible to change the location of a user's .k5login file? 

Answer:
Yes, in /etc/centrifydc/centrifydc.conf please refer to the following parameter:
krb5.conf.k5login.directory
 
This parameter specifies an alternative location for a user’s .k5login files. It has no default setting. If it is not set, the user’s .k5login file will be set as {%home_dir}

/.k5login. If it is set to, say, <k5login_directory>, the user’s .k5login file will be set as <k5login_directory>/<user’s unixname>. 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out? articleKB-6388:In centrifydc.log, what does 'Pool size' and 'busy size' mean? articleKB-1831: runmappers (defunct perl processes) for GPs time out. articleKB-4699: How does Centrify manage Kerberos in Unix/Linux environment? articleKB-4291: What files are modified by Centrify DirectControl or DirectAudit during install & adjoin process articleKB-2569: Ports needed for Centrify Deployment Manager articleKB-4496: Tool to analyze Audit Data articleKB-2380: DirectAudit was unable to establish communication with the DirectAudit daemon. articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0)