Troubleshoot Kerberos in OpsCenter

Troubleshoot OpsCenter Kerberos connections with debug options:

Edit the cluster-specific configuration file, CLUSTER_NAME.conf. The location of this file depends on the type of installation:
- Package installations: /etc/opscenter/clusters/CLUSTER_NAME.conf
- Tarball installations: INSTALL_DIRECTORY/conf/clusters/CLUSTER_NAME.conf
Add the following to the [kerberos] section to output debug messages during Kerberos connections attempts from OpsCenter:
```
[kerberos]
debug = True
```
The debug option outputs the contents of the server section from the jaas-krb5.conf file, informing you of the settings in use that you can verify against your configuration settings.
If deeper debugging is necessary, add -Dsun.security.krb5.debug=true to $OPSC_JVM_OPTS. The JVM parameter outputs verbose information about reasons why Kerberos connections attempts are failing, such as not authenticating due to key expiration, or no keys present in keytab, or cannot find keytab, for example.

For more information about JVM, see Configure the OpsCenter JVM.
Restart OpsCenter.

Give Feedback