Description:
================================================================================
NOTE: See attached Readme document for installation instructions and list of issues resolved in this hotfix.
================================================================================

The TIBCO® API Exchange 2.1.1 Hotfix 003 can be downloaded from the TIBCO Product Support file transfer server,
mft.tibco.com, using your username and password for the TIBCO Support Central website. Please note you should
use an FTP or SFTP client or command-line FTP. TIBCO employees must use a secure protocol.

Server name: mft.tibco.com
Credentials: use your TSC (TIBCO Support Central website) login.
Browser:  https://mft.tibco.com
FTP: port 21
SFTP: port 22

Once logged on you can find the hotfix under:

AvailableDownloads/_Additional_Products/APIExchange/2.1.1/TIB_api-exchange-manager_2.1.1_hotfix03
AvailableDownloads/_Additional_Products/APIExchange/2.1.1/TIB_api-exchange-gateway_2.1.1_hotfix03

================================================================================

TIBCO API Exchange Gateway(R)
=================================================================================

Introduction

Hotfixes are cumulative. This is the third hotfix for TIBCO API Exchange Gateway
product. See the section "Closed Issues in 2.1.1_HF-003" to check the resolved
issues in this hotfix.

=================================================================================
Closed Issues in 2.1.1_HF-003 (This Release)

ASG-6879
TIBCO API Exchange Gateway did not search for the correct format of OAuth access
token in the header of the request.

ASG-6847
The Config UI did not allow the users to login when the authentication was
configured to use LADP server with SSL connectivity.

ASG-6816
The header buffer size was too small when TIBCO API Exchange Gateway processed
the requests using Kerberos SPNEGO authentication mechanism.

ASG-6817
The update configuration did not work for the remote project settings when the
keystore and shared resource files were updated to the master project settings.

ASG-6800
TIBCO API Exchange Gateway did not support the redirect with POST method using
the authorization code flow of OAuth server.

ASG-6794
TIBCO API Exchange Gateway did not support the substitution of ownerID values in
the OAuth authentication policy.

ASG-6786
The Studio could not open the CONSTANTS scorecard for editing.

ASG-6769
TIBCO API Exchange Gateway reset the "403" HTTP status code generated by
the gateway to "500" HTTP status code when the request was sent to the gateway
through the Apache module.

ASG-6711
TIBCO API Exchange Gateway did not support SOAP 1.2 protocol for credential
mapping policies.

ASG-6547
TIBCO API Exchange Gateway OAuth server generated the access token when the
database as backing store was not available.

ASG-6511
TIBCO API Exchange Gateway did not provide an option to specify the OAuth access
token in the header of the request.
To generate the OAuth access token in the request header, specify {access_token}
in  the "headersToForward" field of an facade operation request.

ASG-6399
The updated configuration was incomplete for the OAuth security binding entries
when the user tried to publish the master configuration settings to remote gateway
instances from the portal Config UI of TIBCO API Exchange Manager.

=================================================================================

Closed Issues in 2.1.1_HF-002

ASG-6451
TIBCO API Exchange Gateway did not include the special characters in the parameter
values of the query string for a facade operation request.  

To pass-through the special characters in the parameter values of the query string,  
set the following properties in the ASG_CONFIG_HOME/asg.properties file:

- com.tibco.asg.runtime.http_client.default_uri_format=false
- tibco.clientVar.ASG/Operation/RequiresQueryDecoding=false

ASG-6432
TIBCO API Exchange Gateway did not support a property to set the timeout value
for HTTP native transport when the target service took more than one minute to
send the response to client.
Use the following properties in ASG_CONFIG_HOME/asg.properties to set the
connection timeout value for HTTP, HTTPS, OAuth HTTP, and OAUth HTTPS transports:

tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPConnection/
ConnectionTimeout=60000
tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPSSLConnection/
ConnectionTimeout=60000
tibco.clientVar.DefaultImplementation/Connections/HTTP/OAuthWebappsConnection/
ConnectionTimeout=60000
tibco.clientVar.DefaultImplementation/Connections/HTTP/OAuthWebappsSSLConnection/
ConnectionTimeout=60000

ASG-6431
TIBCO API Exchange Gateway did not set the Content-Length header when the client
sent a HTTP request with 1.0 or 0.9 protocol version.

ASG-6414
TIBCO API Exchange Gateway did not provide a script to purge the log data for
Microsoft SQL Server database.

ASG-6407
TIBCO API Exchange Gateway did not forward the "Authorization" header name to
the target service when the "Headers To Forward" field of the request contained
the "Authorization" header name.

ASG-6392
TIBCO API Exchange returned a misleading "Operation Not Found" error message
when a request with an invalid or missing API Key was sent to the gateway.

ASG-6391
TIBCO API Exchange did not export the data from Spotfire analytics dashboard
to PDF, CSV and PPT formats correctly.

ASG-6276
TIBCO API Exchange Gateway returned an error response when the client sent a
request with no user name and password in HTTP header for HTTP basic
authentication using non-preemptive mode.

ASG-6234
The purge database script for MySQL shipped with TIBCO API Exchange Gateway
may throw a foreign key constraint error.

ASG-6226
The value set in  the "items per page" field under Pagination of Config UI
did not work as expected.
For example, the page entries only displayed 10 entries per page irrespective
of the value set in the "items per page" field.

ASG-6221
Kerberos SPNEGO authentication did not work correctly in TIBCO API Exchange Gateway.

ASG-1193
TIBCO API Exchange Manager displayed an alert error for Linked Data Report
when the report was opened with TIBCO Spotfire. The error report referred to
invalid column in the ASG_TRANSACTION_MESSAGES  table of Central Logger database.

ASG-1103
The Central Logger of TIBCO API Exchange Gateway threw a null pointer exception when
it was deployed in cluster mode.

=================================================================================
Closed Issues in 2.1.1_HF-001

ASG-6243
TIBCO API Exchange Gateway did not handle the responses correctly when content-type
was multipart or mixed.

ASG-6217
TIBCO API Exchange Gateway did not provide the properties on the Config UI to support
SSL V3 for native HTTP channel.

ASG-6215
When AS channels were enabled, TIBCO API Exchange Gateway did not use the
asg.properties file specified with -p parameter of asg-engine command to start
Core Engine, and it searched for ASG_CONFIG_HOME/asg.properties file.

ASG-6195
An error "WSS AuthN Failure - Request is not authenticated with username token"
was thrown by TIBCO API Exchange Gateway if the multiple requests were
processed for WSS authentication.

ASG-6156
TIBCO API Exchange Gateway did not correctly encode the query parameters in the facade
operation URL of northbound request.

ASG-6137
TIBCO API Exchange Gateway did not provide the properties in the
ASG_CONFIG_HOME/asg.properties file to enable the SSLv3 support for the northbound
request received through the native HTTP channel.

To enable SSLV3, set the following property in the ASG_CONFIG_HOME/asg.properties
file:
tibco.clientVar.DefaultImplementation/Connections/HTTP/FacadeHTTPSSLConnection/
SSLServerProtocols=SSLv3,SSLv2,SSLv2Hello

ASG-6114
TIBCO API Exchange Gateway did not log the Client IP, Host, SOAPAction, and
ServiceURI headers of the incoming request at the INFO level.

ASG-6107
The REST serializer of TIBCO API Exchange Gateway used the payload as NULL if the
"Transfer-Encoding: Chunked" header was set instead of the "Content-Length" header.

ASG-6106
When the token API was used to retrieve an access token details, the status of the
access token was shown "Active" in the response message for an expired token.

ASG-5422
TIBCO API Exchange Gateway returned different response messages to clients
when the request was sent to the gateway using the facade HTTP channel instead of
being sent using the Apache module.

ASG-5264
Using the Config UI, when the new target operations are added and saved on
"Target Operation Groups" tab, they were not shown in the "Target Operation Groups"
tab.

================================================================================

TIBCO API Exchange Manager(R)
==================================================================================

Closed Issues in 2.1.1_HF-003 (This Release)

ASG-6399
ConfigUI Master Publish was incomplete for OAUTH Security Bindings Entries.

ASG-6540
When the Swagger UI in API Explorer had no description element at the resourcePath
level, it added it to the JSON file and the description was picked up from the
resourcePath by default.

ASG-6863
The archive option is by default disabled in the backend of Joomla.
To enable it complete the following steps:
1. Click Global Configuration.
2. Select API Manager.
3. Click Enable Archive Objects.

ASG-6864
When trying to archive the environment or API, a long string used to get attached
to the name prevening the archive to work.
This has been fixed.
==================================================================================
Closed Issues in 2.1.1_HF-002

ASG-6439
TIBCO API Exchange did not preserve settings for "PARTNER > Facade Access >
Request Transform and Response Transform" which were configured using the
Config UI when the proxy settings were modified using TIBCO API Exchange Manager
Portal.

ASG-6391
TIBCO API Exchange Manager did not export the data from Spotfire analytics
dashboard to PDF, CSV and PPT formats correctly.

ASG-6287
TIBCO API Exchange Manager threw an exception when the user created or edited
more than one target environment containing more than one API.

ASG-6281
TIBCO API Exchange Manager did not allow the user to edit the application after
a product had been enabled in the application.

==================================================================================
Closed Issues in 2.1.1_HF-001

ASG-6230
The value of Partner Timeout in Facade Access tab was reset to 25 seconds when the
timeout value was updated using the Config UI from TIBCO API Exchange Manager.

ASG-5902
TIBCO API Exchange Manager threw the
"Data truncation: Data too long for column 'content' at  row 1" error for mysql
database when the portal functions were updated.

================================================================================

TIBCO® API Exchange (Gateway and Manager) 2.1.1 Hotfix 003 is now available.

This hotfix applies to the following products and versions: - TIBCO API Exchange Gateway(R) 2.1.1 - TIBCO API Exchange Manager(R) 2.1.1

TIB_api-exchange-gateway_2.1.1_HF-003_readme.txt, TIB_api-exchange-manager_2.1.1_HF-003_readme.txt