Troubleshooting Connector Designer

This topic provides information about troubleshooting issues that you might encounter when using Connector Designer.

Incorrect external CA certificate

Error message:

Failed to reload gateway on https://i2.my-organization:9443
*   Trying 10.1.50.195:9443...
* Connected to i2.my-organization (10.1.50.195) port 9443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /tmp/tmp.RLRUGCtnjv
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [94 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [1750 bytes data]
* TLSv1.2 (OUT), TLS header, Unknown (21):
} [5 bytes data]
* TLSv1.2 (OUT), TLS alert, unknown CA (560):
} [2 bytes data]
* SSL certificate problem: self-signed certificate in certificate chain
* Closing connection 0

Ensure that the CA certificate that you placed in analyze-deployment-tooling/environment-secrets/generated-secrets/certificates/externalCA/CA.cer is correct. You must provide the certificate that signed the Liberty server's certificates in your i2 Analyze deployment.

Incorrect password for adt-admin

Error message:

Failed to reload gateway on https://i2.my-organization:9443
*   Trying 10.1.50.195:9443...
* Connected to i2.my-organization (10.1.50.195) port 9443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /tmp/tmp.ejG1U1t9DV
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
} [512 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.3 (IN), TLS handshake, Server hello (2):
{ [94 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [1750 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS header, Finished (20):
} [5 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS header, Certificate Status (22):
} [5 bytes data]
# ERROR: Validation errors detected, please review the above message(s).
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS header, Finished (20):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Certificate Status (22):
{ [5 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
* ALPN, server accepted to use h2
* Server certificate:
*  subject: CN=i2.my-organization
*  start date: Jul 29 14:47:53 2024 GMT
*  expire date: Nov  1 14:47:53 2026 GMT
*  subjectAltName: host "i2.my-organization" matched cert's "i2.my-organization"
*  issuer: CN=toolkit-ca
*  SSL certificate verify ok.
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* TLSv1.2 (OUT), TLS header, Unknown (23):
} [5 bytes data]
* TLSv1.2 (OUT), TLS header, Unknown (23):
} [5 bytes data]
* TLSv1.2 (OUT), TLS header, Unknown (23):
} [5 bytes data]
* Server auth using Basic with user 'adt-admin'
* Using Stream ID: 1 (easy handle 0x555d46245810)
* TLSv1.2 (OUT), TLS header, Unknown (23):
} [5 bytes data]
> POST /opal/api/v1/gateway/reload HTTP/2
> Host: i2.my-organization:9443
> authorization: [REDACTED_PASSWORD]
> user-agent: curl/7.76.1
> accept: */*
> origin: https://i2.my-organization:9443
> content-type: application/json
> 
* TLSv1.2 (IN), TLS header, Unknown (23):
{ [5 bytes data]
* TLSv1.2 (OUT), TLS header, Unknown (23):
} [5 bytes data]
* TLSv1.2 (IN), TLS header, Unknown (23):
{ [5 bytes data]
* TLSv1.2 (IN), TLS header, Unknown (23):
{ [5 bytes data]
< HTTP/2 401 
< content-language: en
< content-length: 0
< date: Wed, 07 Aug 2024 10:51:33 GMT
< 
{ [0 bytes data]

Ensure that the password for the adt-admin user in the Liberty server is correct. You can check the password in the user.registry.xml file matches the password in the analyze-deployment-tooling/environment-secrets/generated-secrets/application/admin_PASSWORD file.