Re-enter KDC database master key to verify: Īn administrator must be created to manage the Kerberos realm. It is important that you NOT FORGET this password. Master key name will be prompted for the database Master Password.
Initializing database '/var/kerberos/krb5kdc/principal' for realm 'CUSTOMER.HDP', The KDC database is then initialized with the following command, executed from the Master KDC: shell% kdb5_util create -s Supported_enctypes = aes256-cts aes128-cts des-hmac-sha1 des-cbc-md5 arcfour-hmac des-cbc-md5Ĭontents of /var/kerberos/krb5kdc/kpropd.acl: start the KDC and kadmin processes on the Master KDC only: shell% systemctl enable krb5kdc Ĭontents of /var/kerberos/krb5kdc/kadm5.acl: *Ĭontents of the /var/kerberos/krb5kdc/kdc.conf: This file, /etc/nf, must be copied to each node in the cluster. The following defines the KDC configuration for both clusters. The high level information for the article was found at, while the details were worked out through sweat and tears.Įxecute the following command to install the Master and Slave KDC if the KDC is not already installed: yum install krb5-server A use case for this configuration is when a Disaster Recovery cluster is used as a warm standby. This setup will allow two clusters to share a single Kerberos realm, which allows the principals to be recognized between clusters. This article describes the setup of two separate KDCs in a Master/Slave configuration.
0 kommentar(er)
