000038206 - There is no option to clear the mysql-connector-java-{version}-bin.jar file from the MySQL AFX connector template in RSA Identity Governance & Lifecycle

Document created by RSA Customer Support Employee on Dec 5, 2019Last modified by RSA Customer Support Employee on Feb 14, 2020
Version 29Show Document
  • View in full screen mode

Article Content

Article Number000038206
Applies ToRSA Product Set: RSA Identity Governance & Lifecycle
RSA Version/Condition: 6.9.1, 7.0.x, 7.1.0, 7.1.1
IssueSome AFX connector templates require files to be supplied by the customer and uploaded into the RSA Identity Governance & Lifecycle database. Once a file has been uploaded, it may be removed by the Clear button next to the file name under the Loaded column. In the user interface go to AFX > Connector Templates > {connector template name} > File Content tab. For example, in the screenshot below, there is a Clear button next to the jconn3.jar file under the Sybase AFX connector template definition which will remove the jconn3.jar from the database. Also note that this file is not supplied by RSA as indicated by No in the Supplied column.
User-added image

Please see RSA Knowledge Base Article 000030157 -- How to replace an Access Fulfillment Express (AFX) Connector jar file that has been uploaded to an AFX connector template in RSA Identity Governance & Lifecycle for more information on removing uploaded jar files from AFX connector templates.

In the case of the MySQL AFX connector template, there is a known defect where the mysql-connector-java-{version}-bin.jar file needs to be supplied by the customer but the column mistakenly indicates Yes which means supplied by RSA. Furthermore, once the file is uploaded, it cannot be removed as there is no Clear button.
User-added image


User-added image

CauseThis is a known issue reported in engineering ticket ACM-102526.
ResolutionThis issue is being investigated by the Engineering team in order to provide a permanent resolution in a future release.

WorkaroundFor a workaround, please contact RSA Identity Governance & Lifecycle Support  and mention this RSA Knowledge Base Article ID 000038206 for reference.