Congree REST API authorization

The Web API uses OAuth2.0 & OpenId connect as its authentication protocol. The Congree Identity Server acts as the authentication server. It supports password and Trust CMS authorization.

In order to use the Congree REST API, the client has to use the following OAuth parameters:

The authorization endpoint is located at http://<WebAPIHost>/congreeidentityserver. The scope 'termTigerWebAppApi' is only important if you plan to use the CongreeTermTiger API:

Congree password authorization

This authorization method can be used for logging in to Congree using Congree user credentials. The OAuth parameters should be the following:

Trust CMS authorization

This authorization method can be used for logging in to Congree using Trust CMS. The OAuth parameters should be the following: 

For Trust CMS to work, you need to store a password encrypted with base64 in C:\Program Files\Congree Language Technologies GmbH\Congree Identity Server\appsettings.json and to use it in your token request (in plain text form).

{
  "Logging": {
    "LogLevel": {
      "Default": "Warning"
    }
  },
  "AllowedHosts": "*",
  "Congree": {
    "TrustCMSSecret": "YW55MTIz"
  }
}

Support third-party identifiers

The Identity server supports third-party systems, which are configured in the Congree Control Center. For now, only identifiers for the Congree Bulk Check Service are supported. To work with third-party identifiers, you should use the following additional parameter: 

Third-party systems support all authorization methods. If the specified parameter is not used, default Congree Bulk Check Service settings will be used.