You can troubleshoot Automation Orchestrator plug-in problems by modifying the Kerberos configuration file used by the plug-in.

The Kerberos configuration file is located in the /data/vco/usr/lib/vco/app-server/conf/ directory of the Automation Orchestrator Appliance.

Procedure

  1. Log in to the Automation Orchestrator Appliance command line as root.
  2. Run the kubectl -n prelude edit deployment vco-app command.
  3. In the deployment file, locate and edit the -Djava.security.krb5.conf=/usr/lib/vco/app-server/conf/krb5.conf' string. 
    -Djava.security.krb5.conf=/usr/lib/vco/app-server/conf/krb5.conf -Dsun.security.krb5.debug=true'
  4. Save the changes and exit the file editor.
  5. Run the kubectl -n prelude get pods command.
    Wait until all pods are running.
  6. Verify that the Kerberos debug logging is enabled. 
    kubectl -n prelude log {vco_app_name} -c vco-server-app | grep krb5
    Verify that the logs contain a similar message. 
    kubectl -n prelude log vco-app-5c965f9b9d-v8srd -c vco-server-app | grep krb5
12:23:05,417 INFO O11N:75 - Sysprop: java.security.krb5.conf = /usr/lib/vco/app-server/conf/krb5.conf
12:23:05,421 INFO O11N:75 - Sysprop: sun.security.krb5.debug = true
2019-10-22 12:23:38.521+0000 [Thread-19] INFO {} [O11N] Sysprop: java.security.krb5.conf = /usr/lib/vco/app-server/conf/krb5.conf
2019-10-22 12:23:38.525+0000 [Thread-19] INFO {} [O11N] Sysprop: sun.security.krb5.debug = true
Java config name: /usr/lib/vco/app-server/conf/krb5.conf
EType: sun.security.krb5.internal.crypto.Aes256CtsHmacSha1EType