This section lists the prerequisites and steps for applying this patch.

Though every release of Adeptia comes with seamless upgrades and bug-free patches. For customer's complex use cases, we recommend applying the patch in a non-production environment first followed by testing. After the use cases run successfully without any errors or warnings, you can apply the patch in the production environment.

Prerequisites

Ensure that you have:

Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>.
Connect Server services are running.
Connect Portal service is stopped.

Applying the patch

For Windows

Extract the Adeptia Connect zip file from the downloaded folder.
Open the Command Prompt.
Go to the folder where you have extracted the zip file.

Run the following command to apply the patch:

Apply-Patch.bat -portal “<Path where Connect Portal is installed till ConnectPortal folder>”

For example:

Apply-Patch.bat -portal  "C:/Program Files/AdeptiaConnect/AdeptiaConnect-x.x/ConnectPortal"

Once the patch is applied, a confirmation message will be displayed.

For Linux

Open the Terminal.
Extract the downloaded zip file in a directory.
Go to the directory where you have extracted the zip file.

Run the following command to apply the patch:

./Apply-Patch.sh -portal <Path where Connect Portal is installed till ConnectPortal folder>

For example:

./Apply-Patch.sh -portal /mnt/AdeptiaConnect-x.x/ConnectPortal

Once the patch is applied, a confirmation message will be displayed.

Post Patch Deployment Steps

In this release, some manual changes are required in Connect Portal.

Changes in web.xml File

Go to …<ConnectPortalInstallFolder>\conf location.
Take backup of web.xml file from the above-mentioned location.
Go to the downloaded Adeptia Connect zip folder and rename the web.xml_Portal file to web.xml.
Copy the renamed web.xml file.
Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\conf.

Open web.xml file and do the following changes:

You need to uncomment the below tag. This is required only when you auto redirect from http to https.

<!-- <filter>
	<filter-name>RedirectToHttpsFilter</filter-name>
	<filter-class>com.adeptia.connect2.embedded.tomcat.web.RedirectToHttpsFilter</filter-class>
</filter>
<filter-mapping>
	<filter-name>RedirectToHttpsFilter</filter-name>
	<url-pattern>/*</url-pattern>
</filter-mapping>

<security-constraint>
	<user-data-constraint>
		<transport-guarantee>CONFIDENTIAL</transport-guarantee>
	</user-data-constraint>
</security-constraint> -->

Save the file.

Changes in server.xml File

Go to …<ConnectPortalInstallFolder>\conf location.
Take backup of server.xml file from the above-mentioned location.
Open server.xml file.
Go to Connector port section and do the following changes:
1. Update the property 'sslProtocol' value as TLSv1.2.
2. Add this property sslEnabledProtocols="TLSv1.2" as shown below.
Save the file.

Changes in securityContext.xml File

Go to …<ConnectPortalInstallFolder>\resources_config\saml location.
Take backup of securityContext.xml file from the above-mentioned location.
Go to the downloaded Adeptia Connect zip folder and copy securityContext.xml file.
Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config\saml.
Open securityContext.xml file.
Do the same manual changes that you have done in your previous securityContext.xml file (that you had saved as a backup).

In case you are using SAML authentication then open the replaced securityContext.xml file and do the following changes:

Uncomment the following property:

<!-- <property name="entityBaseURL" value="http://localhost:8080/adeptia"/> -->

Update the URL as required. Where localhost is the IP address and port of the Connect Server.
Uncomment the idp.xml property:

If you are using Adeptia Connect with load balancer, follow these steps:

Remove or comment out the existing contextProvider bean
<bean id="contextProvider" class="org.springframework.security.saml.context.SAMLContextProviderImpl"/>

Add the below contextProvider bean

<bean id="contextProvider" class="org.springframework.security.saml.context.SAMLContextProviderLB">
 <property name="scheme" value="http"/>
 <property name="serverName" value="www.myserver.com"/>
 <property name="serverPort" value="8080"/>
 <property name="includeServerPortInRequestURL" value="false"/>
 <property name="contextPath" value="/adeptia"/>
</bean>

This table explains the each property of contextProvider bean:

Property Name	Description
scheme	Name of the scheme (http or https).
serverName	Name of the server.
serverPort	Port number of the server.
includeServerPortInRequestURL	To include server port number in the URL or not. It must be false.
contextPath	Prefix of a URL path used to select the context(s) to which an incoming request is passed. A URL is in the format: h ttp://hostname.com/contextPath/, where each of the path elements can be zero or more separated elements. It must be /adeptia.

It will look like:

<bean id="contextProvider" class="org.springframework.security.saml.context.SAMLContextProviderLB">
 <property name="scheme" value="http"/>
 <property name="serverName" value="www.myserver.com"/>
 <property name="serverPort" value="8080"/>
 <property name="includeServerPortInRequestURL" value="false"/>
 <property name="contextPath" value="/adeptia"/>
</bean>

If there were any other changes in the old file, you have to do the same changes manually in the replaced securitycontext.xml file.
Save the file.
Restart Connect Portal.

Changes in apps.properties File

Go to …<ConnectPortalInstallFolder>\resources_config location.
Take backup of apps.properties file from the above-mentioned location.
Go to the downloaded Adeptia Connect zip folder and copy apps.properties file.
Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config.
Open apps.properties file.
Do the same manual changes in the file that you have done in your previous apps.properties file (that you had saved as backup).
Save the file.

Once the post installation steps are done, start the Connect Portal.

If you are using Database/Advanced Database Event, Source/Target activity with MySQL Database Server using an older version of MySQL JDBC jars then it is recommended to upgrade the jars to mitigate the vulnerability associated with the older jars.

Click here to download the recommended version of MySQL jars (mysql-connector-java-8.0.18.jar) and follow the steps to upgrade it.

Next Step

Verifying Patch

See also

Recovering Connect Portal

Browser not supported