inRiver Translation Connector
  • Introduction
  • Architecture
  • Workflow
  • Install - inRiver PMC
  • PMC install - inRiver Data Model Configuration
  • Updating Connector - inRiver iPMC
  • Install - inRiver 6.3
  • On-premise (6.3) Install - inRiver Data Model Configuration
  • Translation Configuration
    • Sample Translation Configuration
  • Language Configuration
  • Using the Lionbridge Connector (Manual Workflow)
    • Entity Translation Status
    • Translation Job Status & Actions
    • Linked Entities Translation Status
    • Cancelling Translation Jobs
    • Deleting Translation Jobs
    • Translation of CVL values
    • Translation of Specifications
    • Sending Entity Images for Reference.
    • Sending non-LocaleStrings for Reference
  • Using the Lionbridge Connector (Automatic workflow)
  • Appendix 1: Lionbridge Language List
  • Appendix 2: Troubleshooting
  • Upgrade - 6.3 > PMC
  • Upgrade - 6.3
  • Upgrade - 3.2.2 -> 3.3
    • inRiver 6.3
    • inRiver PMC
  • Language Configuration - Upgrading
  • Logging
  • Criteria Configuration
    • Criterias
  • TLS 1.2
  • Release Notes
Powered by GitBook
On this page

TLS 1.2

This page details how to configure the Lionbridge inRiver Connector to use TLS 1.2

PreviousCriteriasNextRelease Notes

Last updated 4 years ago

Steps to follow to configure the connector to use TLS 1.2 when TLS1.0/1.1 is depreciated:

  1. Within inRiver Connect folder, locate the "inRiver.integration.exe.config" file and open with a text editor like Notepad etc.

2. In the <runtime> section, insert the line "<AppContextSwitchOverrides value="Switch.System.Net.DontEnableSystemDefaultTlsVersions=false" />"

3. Open Internet Options, either via IE browser or Control Panel.

4. Select the "Advanced" tab and ensure that "Use TLS 1.2" is selected.

5. Restart the inRiver Connect 6 Services.

inRiver.integration.exe.config file