Configure External Login with Trust AD

Set up Trust AD in Congree Deployment Assistant

Run the Congree Deployment Assistant
Enter configuration

Switch to Server side

Enter the Identity Server Configuration

Activate Trust AD

Deploy Congree-Redirect App

Create a folder called C:\Program Files\Congree Language Technologies GmbH\Congree Redirect App

Unzip this archive into that folder:

Change file C:\Program Files\Congree Language Technologies GmbH\Congree Redirect App\assets\appconfig.json

{
    "AUTH_URL": "https://yourserver/congreeidentityserver",
    "CLIENT_ID": "CongreeWebAPI",
    "REDIRECTPAGE": "https://servername/CongreeRedirect/redirect-page",
    "SCOPE": "webApi offline_access openid",
    "ACR_VALUES": "idp:external"
}

Adjust Identity Server

Open file C:\Program Files\Congree Language Technologies GmbH\Congree Identity Server\appsettings.json

Make sure the section RedirectUris contains this line:

“https://servername/CongreeRedirect/redirect-page”

In the end it should look something like this:

      "ClientId": "CongreeWebAPI",
      "RedirectUris": [
        "http://servername/CongreeControlCenter/auth-callback",
        "http://servername/CongreeControlCenter/auth-callback",
        "https://servername/CongreeControlCenter/auth-callback",
        "https://servername/CongreeControlCenter/silent-callback",
		"https://servername/CongreeIndie/signin-callback",
		"https://servername/CongreeAnywhere/signin-callback",
		"http://servername/CongreeAnywhere/signin-callback",
        “https://servername/CongreeRedirect/redirect-page”
		"http://localservernamehost/CongreeIndie/signin-callback",
		"https://servername/CongreeOIDC/redirect-page",
		"https://servername/CongreeWord/signin-callback.html"
      ],

Add application to IIS

Open the IIS Manager
Expand the tree until you see Default Web Site
Right click Default Web Site and click Add Application…
1. Alias: CongreeRedirect
2. Physical path: C:\Program Files\Congree Language Technologies GmbH\Congree Redirect App
Confirm with OK

Set up Congree groups

In Congree Control Center/User/Groups make sure you have a group with your domain configured

Configure the Browser Extension Connection Settings

To use the Congree Browser Extension with predefined settings, you need to configure C:\Program Files\Congree Language Technologies GmbH\Congree Web Interface\cwi-extension-config.json on the server side

In this file you can set up all the configurations you want to have available in Congree Extension. It can look something like this:

[
  {
    "name": "Congree Config",
    "loginType": "usernamePassword",
    "accessTokenUrl": "https://yourserver/congreeidentityserver/connect/token",
    "serverUrl": "https://yourserver/Congree",
    "thirdPartySystemsIdentifier": "",
    "pagesToBeChecked": [
      {
        "name": "https://www.facebook.com",
        "ruleset": "Compathy_Facebook"
      },
      {
        "name": "https://bing.com",
        "ruleset": "Congree Standard"
      }
    ]
  },
  {
    "name": "Trust CMS Config",
    "loginType": "cms",
    "accessTokenUrl": "https://yourserver/congreeidentityserver/connect/token",
    "serverUrl": "https://yourserver/Congree",
    "thirdPartySystemsIdentifier": "anywhere",
    "pagesToBeChecked": [
      {
        "name": "https://google.com",
        "ruleset": "Congree Standard"
      }
    ]
  },
  {
    "name": "External Config",
    "loginType": "external",
    "accessTokenUrl": "https://yourserver/CongreeOIDC",
    "serverUrl": "https://yourserver/Congree",
    "thirdPartySystemsIdentifier": "",
    "pagesToBeChecked": []
  }
]

Configuring the file

Parameter	Description

Parameter	Description
name	This is the names displayed to the user in the picklist “Configuration”. Choose a name that tells the user quickly what this option does
loginType	There are three login types you can configure: usernamePassword This will require that the user has an account in Congree and that their credentials are provided to them. cms This allows the user to select any username they want but they will need to know the trust CMS secret to be able to connect. Provide it to them like you would a password. You should know your companies TrustCMS secret and can otherwise access it here: C:\Program Files\Congree Language Technologies GmbH\Congree Identity Server\appsettings.json external This will require a correct setup in Congree Deployment Assistant to accept an external login. Congree is then not involved in the process of providing credentials and only awaits a successful login
accessTokenUrl	This is the URL Congree needs to know to handle login. This URL is already correct and you should not have to modify it.
serverUrl	This is the URL where Congree will find its server. This URL is already correct and you should not have to modify it.
thirdPartySystemsIdentifier	Provide a third-party identifier if you know what this is and if you need it. Find more information here: Settings Manager: Third-Party Systems
pagesToBeChecked	In this section you can add names and rulesets to define what pages should already have a rule set from the start. Users can augment this later
name	This is the url where you want Congree to check from the start
ruleset	This is the rule set Congree should use on the URL you just specified.

Updating Congree

When you update Congree this file will be overwritten. So once you are happy with your file, store it somewhere and remember to replace it after updating Congree.

Congree Browser Extension - Administrator