Main index | Section 8 | Options |
to the /etc/krb5.conf configuration file and make sure kcm is started in the system startup files.[libdefaults] default_cc_name = KCM:%{uid}
The kcm daemon can hold the credentials for all users in the system. Access control is done with Unix-like permissions. The daemon checks the access on all operations based on the uid and gid of the user. The tickets are renewed as long as is permitted by the KDC's policy.
The kcm daemon can also keep a SYSTEM credential that server processes can use to access services. One example of usage might be an nss_ldap module that quickly needs to get credentials and doesn't want to renew the ticket itself.
Supported options:
| |
system cache name | |
| |
location of config file | |
| |
system cache group | |
| |
max size for a kcm-request | |
| |
disallow extracting any krbtgt from the kcm daemon. | |
| |
detach from console | |
| |
system principal name | |
| |
lifetime of system tickets | |
| |
octal mode of system cache | |
| |
disable credentials cache name constraints | |
| |
renewable lifetime of system tickets | |
| |
path to kcm domain socket | |
| |
path to kcm door socket | |
| |
server to get system ticket for | |
| |
system keytab name | |
| |
system cache owner | |
| |
Heimdal | KCM (8) | May 29, 2005 |
Main index | Section 8 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | LISP = Lots of Irritating Silly Parentheses | ” |