This section lists the prerequisites and steps for applying this patch.
Prerequisites
Ensure that you have:
- Read and Write permissions on all subfolders and files of .../AdeptiaConnect-<Version>.
- Take backup of shutdown.sh file from …<ConnectPortalInstallFolder>\bin location. This file will help you to update the new stop.sh file for manual changes, if you have done any. This is applicable only for Linux environment.
- Connect Server services are running.
- Connect Portal service is stopped.
Steps to update the patch:
Post Patch Deployment Steps
In this release, some manual changes are required in Connect Portal.
Changes in Web.xml File
- Go to the folder path where Adeptia Connect is installed. For example, C:\Program Files\AdeptiaConnect\AdeptiaConnect-3.0\ConnectPortal\conf
- Take back up of web.xml file from the above-mentioned location.
- Go to the downloaded Adeptia Connect zip folder and copy web.xml.
- Replace the existing file with the copied file at the following location …<ConnectPortalInstallFolder>\conf.
- Open the replaced file and do the following changes:
- If you had uncommented the following tag in the replaced file will comment it, therefore you need to uncomment it again:
<!--<security-constraint>
<web-resource-collection>
<web-resource-name>Protected Context</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>-->
- If you had uncommented the following tag in the replaced file will comment it, therefore you need to uncomment it again:
- 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.
- Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config\saml.
- Do the same manual changes that you have done in your previous securityContext.xml file (that you had saved as 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:
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: http://hostname.com/contextPath/, where each of the path elements can be zero or more separated elements. It must be /adeptia. Property NameDescriptionIt 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> - Remove or comment out the existing contextProvider 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 catalina.properties File
- Go to …<ConnectPortalInstallFolder>\conf location.
- Take backup of catalina.properties file from the above-mentioned location.
- Go to the downloaded Adeptia Connect zip folder and copy catalina.properties file.
- Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\conf.
- Do the same manual changes that you have done in your previous catalina.properties file (that you had saved as backup).
Changes in stop.sh File
In case, you have done manual changes in the shutdown.sh file then follow the below step (Applicable only for Linux environment):
- Go to …<ConnectPortalInstallFolder>\bin location.
- Open stop.sh file.
- Do the same manual changes in file that you have done in your previous shutdown.sh file (that you had saved as backup).
Follow the steps to provide the execute permission on stop.sh file. This step is mandatory irrespective of manual changes in shutdown.sh file.
- Go to …<ConnectPortalInstallFolder>\bin location.
- Type the command chmod +x stop.sh to get the execution permission on stop.sh file.
Next Steps