Resolution:
Description:
============

TIBCO Businessworks (BW) application using HTTP basic authentication fails to authenticate the user when deployed in Administrator domain using EMS transport, database backend and Vendor supplied JDBC drivers (eg Oracle Thin driver)

Environment:
===========

TIBCO Runtime Agent(TRA) 5.x.x
TIBCO BusinessWorks (BW) 5.x.x
Vendor Supplied JDBC drivers (eg. Oracle Thin driver etc)

Symptoms:
========

1). A TIBCO BusinessWorks deployed application having an HTTP receiver (with basic authentication enabled) fails with the following message when deployed in Administrator domain (having Database backend, EMS transport and Vendor supplied JDBC drivers):

************************************************************************
Info [BW_Plugin] BW-HTTP-100700 Authentication attempt [user=admin, deployment=TestBW-HTTPArchive, authentication_succeeded=false]
************************************************************************

2). A user can logon to TIBCO Administrator using the username and password specified in the Identity resource configuration in the HTTP client process.

Cause:
====

This issue is caused due to an existing defect in BusinessWorks:

BW-9193 : HTTP Authentication not working when Admin uses EMS transport with Oracle OCI driver, But works with Tibco Driver

The BW engine is unable to find the Vendor JDBC drivers in the classpath resulting in an authentication failure.

Resolution:
==========

The following steps will resolve this issue:

1). Edit the bwengine.tra file on the machine where the application is deployed under $TIBCO_HOME/bw/5.x/bin folder by adding the ORACLE_CLIENT_HOME to the following path and classpath properties:

tibco.env.PATH
tibco.env.STD_EXT_CP

2). Re-build the EAR file in Designer and then deploy it in Administrator.

TIBCO BusinessWorks (BW) applications using HTTP basic authentication fails even though the correct username and password are supplied when an Oracle Thin JDBC driver is used for DB based Authentication.