This section lists the prerequisites and steps for applying and verifying 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

Applying the patch

  1. Extract the Adeptia Connect zip file from the downloaded folder.
  2. Open the Command Prompt.
  3. Go to the folder where you have extracted the zip file.
  4. 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-x.x/ConnectPortal"
     
    Once the patch is applied, a confirmation message will be displayed. 


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

  4. 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.

After applying this patch, refer to post patch deployment section for manual changes.

Post patch deployment steps

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

Changes in securityContext.xml file

  1. Go to …<ConnectPortalInstallFolder>\resources_config\saml location.

  2. Take backup of securityContext.xml file from the above-mentioned location. (remove the prerequisites step for backup)

  3. Go to the downloaded Adeptia Connect zip folder and rename the securityContext.xml_Portal file to securityContext.xml.
  4. Copy the renamed securityContext.xml file.
  5. Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config\saml.

  6. Go to Security for the administration UI section and make the following change:

    1. Add the below property under the security headers tag:
      <security:hsts max-age-seconds="31536000"/>



  7. Go to Secured pages with SAML as entry point section and make the following change:
    1. Add the below property under the security headers tag:
      <security:hsts max-age-seconds="31536000"/>


  8. In case you are using SAML authentication, open the updated securityContext.xml file and do the following changes:

    1. Uncomment the following property:

      <!-- <property name="entityBaseURL" value="http://localhost:8080/adeptia"/> -->
    2. Update the URL as required. Where localhost is the IP address and port of the Connect Portal.
    3. Uncomment the idp.xml property:



    4. 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:

      schemeName of the scheme (http or https).
      serverNameName of the server.
      serverPortPort number of the server.
      includeServerPortInRequestURLTo include server port number in the URL or not. It must be false.
      contextPathPrefix 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 Name

      Description

      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>

  9. If there were any other changes in the old file, you have to do the same changes manually in the replaced securityContext.xml file.

    For older changes, refer to the old securityContext.xml file that you had saved as a backup.


  10. Save the file.

  11. Restart the Connect Portal.

Changes in apps.properties file

  1. Go to …<ConnectPortalInstallFolder>\resources_config location.

  2. Take backup of apps.properties file from the above-mentioned location. (remove the prerequisites step for backup)

  3. Go to the downloaded Adeptia Connect zip folder and copy the apps.properties file.
  4. Replace the existing file with the copied file at the following location: …<ConnectPortalInstallFolder>\resources_config.
  5. Open apps.properties file.
  6. Explain the new changes.

  7. If there were any other changes in the old file, you have to do the same changes manually in the updated apps.properties file.

    For older changes, refer to the old apps.properties file that you had saved as a backup.


  8. Save the file.

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

Verifying Connect Portal patch

Login to Adeptia Connect. If you log in successfully, indicates Connect Portal is updated successfully.