Egress to CONNECT data services

If you plan to egress data to CONNECT data services, use a token endpoint. This allows entering client credentials once in AVEVA Edge Management rather than in each applicable section in the configuration file.

To do this, define the token endpoint in the applicable configuration sections (DataEndpoints, HealthEndpoints, or both).

For example:

{

"id": "CONNECT data services",

"endpoint": "https://<CONNECT data services OMF endpoint>",

"clientId": "none",

"clientSecret": "{{none}}",

"tokenEndpoint": "http://localhost:5005/api/v1/emm/identity/token"

}

The fields for id, endpoint, clientId, and clientSecret can contain any information, but tokenEndpoint must be exactly as written to use the module’s token endpoint.

If you do not wish to use a token endpoint, you can specify the clientId in the configuration file and make use of reference secrets in order to securely transmit the secret value to the device. See How to reference secrets for more details.