Egress endpoint parameters
- Last UpdatedAug 26, 2024
- 2 minute read
You can configure the following AVEVA Events to CONNECT Egress endpoint parameters:
|
Parameter |
Required |
Type |
Description |
|---|---|---|---|
|
Id |
Optional |
string |
Unique identifier for the endpoint. Allowed value: any string identifier Default value: new GUID |
|
Endpoint |
Required |
string |
Destination that accepts event messages. Supported destinations include CONNECT data services. The value entered must comprise a well-formed HTTP or HTTPS endpoint string similar to the following: https://{%AvevaCONNECTdataservicesDomain%}/api/v1/Tenants/{%tenant ID%}/Namespaces/{%Namespace Guid%} Allowed value: well-formed HTTP or HTTPS endpoint string Default value: null Notes: |
|
ClientId |
Required |
string |
Authentication with the CONNECT data services endpoint. Allowed value: any string, can be null if the endpoint URL schema is HTTP Default value: null Note: For more information on setting up AVEVA CONNECT clients, refer to the CONNECT data services online help. |
|
ClientSecret |
Required |
string |
Authentication with the CONNECT data services endpoint. Allowed value: any string, can be null if the endpoint URL schema is HTTP Default: null |
|
TokenEndpoint |
Optional |
string |
Retrieves a CONNECT data services token from an alternative endpoint. Allowed value: well-formed http or https endpoint string Default value: null |
|
ValidateEndpointCertificate |
Optional |
boolean |
Disables verification of destination certificate. Note: Only use for testing with self-signed certificates. Allowed value: true or false Default value: true |
