What to do when you see "Host is not authenticated" when deploying BE application in TEA.

What to do when you see "Host is not authenticated" when deploying BE application in TEA.

book

Article ID: KB0083345

calendar_today

Updated On:

Products Versions
TIBCO BusinessEvents Enterprise Edition 5.3.0 5.4.0

Description

You will see this error when the be-agent.props file has incorrectly configured a private key file for password-less SSH authentication in the SSH section of configuration.

Issue/Introduction

When deploying a Business Events (BE) application in TIBCO Enterprise Administrator (TEA) with certain configurations, you may see an error message of "Host is not authenticated".

Environment

All

Resolution

Either there is no entry for "be.tea.agent.ssh.privatekey.file=" or the entry is not readable from the machine the BE TEA agent is running on. If the entry is not readable you will see the following error in the BE TEA agent log file:

10 Aug 2017 17:49:53,145 EDT -0400 DEBUG jsch_group_op-0 [com.tibco.cep.bemm.management.util.ManagementUtil] - Attempting authentication to tibco@10.38.5.126:22 using PRIVATE KEY '/home/tibco/.ssh/id_rsa/wu-pricing-tibco.pem'
10 Aug 2017 17:49:53,156 EDT -0400 DEBUG jsch_group_op-0 [com.tibco.cep.bemm.common.pool.GroupJob] - java.io.FileNotFoundException: /home/tibco/.ssh/id_rsa/wu-pricing-tibco.pem (Permission denied)

 
Powered by Wolken Software