Contact an Expert

Bringing powerful connections to your supply chain pays—and it’s not as complicated as you might think. Reach out to an Elemica consultant and see how you can start transforming your supply chain today.

qlconnect.cob.elemica.com

Elemica Test Environment Certificate

The Test environment certificate was renewed on May 8th, 2024.

Certificate Effective Date

May 8, 2024

Certificate Subject

CN = qlconnect.cob.elemica.com
O = Elemica, Inc.
L = Wayne
S = Pennsylvania
C = US

SSH Key Fingerprint

30:30:c6:e6:5c:a6:b3:76:00:4f:70:f8:a6:a8:1f:80

Certificate Expiration Date

‎‎May ‎11, ‎2025


Download Certificate


IP: 54.155.93.234

FTPs and SFTP/SSH

Partners connecting with Elemica Test/COB environments via qlconnect.cob.elemica.com may be required to add/update the SSH fingerprint / RSA key depending on your application settings.

For example, your application may prompt you to manually accept the fingerprint/RSA key when connecting to Elemica TEST/COB environment. In some applications, you will need to delete the old certificate/RSA key before your application prompts you to accept the new certificate/RSA key.

No action is required if Elemica is doing the message pulling/pushing to your application.

HTTPS, AS2 or ebXML

Certificates are required for partners connected to qlconnect.cob.elemica.com via HTTPS, AS2, or ebXML. For AS2 this certificate is for https connectivity, signing, and encryption.

Elemica’s TEST AS2IDs: 878542765HT or 878542765T

*Please be advised the above AS2IDs are for reference only. You must verify which Elemica AS2ID is associated to the current certificate before changing.

The certificate chain may contain CA and Root certificates that is new to your certificate repository. Please verify if the certificates need to be installed and make sure a cache refresh/restart is performed after certificate change.

Special Directions for RNO/RNIF

RNO partners will need to update two different certificates.

  1. Connectivity / ssl authentication – qlconnect.cob.elemica.com
  2. Signing - Please use the below certificates depending on your connection agreement

FTP

Not applicable