...

Anchor
Prerequisites Prerequisites

Prerequisites

• Read and Write permissions on all sub-folders and files of .../AdeptiaConnect-<Version>. 
• Take backup of launcher.properties file from …<ConnectPoratlInstallFolder>\conf location. This backup file will help you replicate the manual changes in case you have done earlier in the launcher.properties file before applying this patch.  
• Take backup of securityContext.xml file from …<ConnectPortalInstallFolder>\resources_config\saml location. This backup file will help you replicate the manual changes in case you have done earlier in the securityContext.xml file before applying this patch.  
• Take backup of apps.properties file from …<ConnectPortalInstallFolder>\resources_config location. This backup file will help you replicate the manual changes in case you have done earlier in the apps.properties file before applying this patch.    
  
• Connect Server services are running.
  
• Connect Portal service is stopped.
• Ensure that you have followed the Prerequisites' instructions given on the Upgrade page.
  

Anchor
Applying the patch Applying the patch

Applying the patch

...

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

Changes in

...

launcher.

...

properties file

1. Go to the downloaded Adeptia Connect zip folder and rename the securityContext.xml_Portal file to securityContext.xml.
2. Copy the renamed securityContext.xml file.
3. Replace the existing file with the copied file at the following location: …to …<ConnectPoratlInstallFolder>\conf location.
4. Open launcher.properties file.
5. Do the same manual changes in the file that you have done in your previous launcher.properties file (that you had saved as a backup). For example, you may need to update the JVM settings and Truststore location as they are there in the backup file.
6. Save the file.

Changes in securityContext.xml file

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

2. In case you are using SAML authentication, open the updated Open securityContext.xml file and do .

3. Go to Security for the administration UI section and make the following

   changes

   change:

   1. Uncomment Add the following below property under the security headers tag:
      

      <!-- <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.
   Uncomment the idp.xml property:
   Image Removed
   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>

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

4. Restart the Connect Portal.

Changes in apps.properties file

...

Replace the details for Microsoft SharePoint by the details given below:

microsoftsharepoint.oauthVersion=2.0
microsoftsharepoint.oauth20.authorize={baseUrl}/_layouts/15/OAuthAuthorize.aspx
microsoftsharepoint.oauth20.accessToken=https://accounts.accesscontrol.windows.net/{realmId}/tokens/OAuth/2
microsoftsharepoint.scope=Site.Manage List.Manage Web.Manage Web.Write AllSites.Manage AllProfiles.Manage
microsoftsharepoint.AccessTokenValueMap=resource$00000003-0000-0ff1-ce00-000000000000/{domain}.sharepoint.com@{realmId}

...

1. 1. <security:hsts max-age-seconds="31536000"/>
      
      Image Added
      
      
2. 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"/>
      
      Image Added
      
      

3. Save the file.

Changes in apps.properties file

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

2. Open apps.properties file.

3. Search for QuickBooks app section and replace the existing code block with the one given below:

   Code Block
   title QuickBooks
   quickbooks.appKey= quickbooks.appKeySecret= quickbooks.oauthVersion=2.0 quickbooks.oauth20.accessToken=https://oauth.platform.intuit.com/oauth2/v1/tokens/bearer quickbooks.oauth20.authorize=https://appcenter.intuit.com/connect/oauth2 quickbooks.oauth10.requestToken=https://oauth.intuit.com/oauth/v1/get_request_token quickbooks.oauth10.authorize=https://appcenter.intuit.com/Connect/Begin quickbooks.oauth10.accessToken=https://oauth.intuit.com/oauth/v1/get_access_token quickbooks.openId.provider=https://openid.intuit.com/OpenId/Provider quickbooks.openId.identity=http://specs.openid.net/auth/2.0/identifier_select quickbooks.scope=com.intuit.quickbooks.accounting quickbooks.enableProduction=true

   
   

4. Search for Xero app section and replace the existing code block with the one given below:
   
   

   Code Block
   title Xero
   xero.appKey= xero.appKeySecret= xero.oauthVersion=2.0 xero.oauth.signatureMethod=RSA-SHA1 xero.oauth20.accessToken=https://identity.xero.com/connect/token xero.oauth20.authorize=https://login.xero.com/identity/connect/authorize xero.oauth10.requestToken=https://api.xero.com/oauth/RequestToken xero.oauth10.accessToken=https://api.xero.com/oauth/AccessToken xero.oauth10.authorize=https://api.xero.com/oauth/Authorize xero.refreshToken=https://api.xero.com/oauth/AccessToken xero.clientAuthentication=true xero.clientKeystore=xeroapps.p12 xero.clientKeystoreType=PKCS12 xero.clientKeystorePassword= xero.clientKeystorePrivateKeyPassword= xero.privateKey= xero.scope=offline_access accounting.transactions accounting.settings accounting.contacts payroll.employees xero.enableProduction=true

   
   

5. Save the file.
6. Restart the Connect Portal.

Anchor
Verifying Connect Portal patch Verifying Connect Portal patch

Verifying Connect Portal patch

...

To verify if the Connect Portal has been deployed successfully, login to the portal and check the build tag of the Connect Portal.

Follow the steps below to check the build tag:

1. Click Help > About.
2. On the About screen, check the Connect Portal tag. 
   If the build tag matches the tag of the Connect Portal, it indicates that the Connect Portal patch is deployed successfully.

Additionally, to verify if the user interface of the Connect Server is working as expected, follow the steps below:

• Click Configure > Developer Studio > Proceed.
  If you are able to interact with the Connect Server interface, it indicates that the Connect Server is updated.