/
Server to Server Entrust Certificate Change

Server to Server Entrust Certificate Change

In line with the security industry best practice, Symantec-issued SSL/TLS certificates will be deprecated. To mitigate this, the following URLs will have the SSL/TLS certificates replaced with Entrust certificates:


On this page:


Important Change Information for Qvalent/Westpac/St. George Customers

This page contains advice that must be actioned to ensure no loss of banking service with the QuickStream, iLink and QuickSuper Qvalent/Westpac/St. George products

Who might this change affect?

Any customer application which:

  • Connects to any of the following URLs hosted by Qvalent used by our QuickStream, PayWay, QuickSuper API and/or iLink products, and

  • Does not already have the relevant Entrust certificate authority added to the application's SSL/TLS trust store.

URL

Product(s)

URL

Product(s)

https://ws.qvalent.com (Production Environment)

[COMPLETED 02/05/2022]

QuickSuper API

SOAP Services

QuickStream QuickWeb Secure Token Request

QuickStream QuickConnect Secure Token Request

iLink SOAP and HTTPS file transfer

https://ssiw.qvalent.com (Production Environment)

[COMPLETED 06/06/2022]

iLink (Legacy HTTPS file transfer)

Note: on port 443 only, this does not include SFTP (port 22).

https://ccapi.client.qvalent.com (Production Environment)

[SCHEDULED FOR 04/07/2022]

QuickStream - QuickGateway

PayWay Classic API

Why is Qvalent/Westpac/St. George making this change?

Trust for all SSL/TLS certificates issued by Verisign/Symantec Roots is being deprecated in September 2018 in new releases of their Internet browser applications. Additionally, DigiCert who purchased Verisign/Symantec will stop issuing cross chains to the old Versign roots in early 2022. This means that we will no longer be able to request certificates with this cross-chain.

Qvalent has made the decision to move to Entrust as our new provider of SSL/TLS certificates for these hosts. This means changing the structure of the certificates on these hosts which may result in distrust by applications.

When will this change be made?

Qvalent plans to make the certificate changes at the following dates/times:

URL

Date and Time

URL

Date and Time

http://ws.qvalent.com

(Production Environment)

Monday 2nd May 2022 @ 10:00am AEST

[COMPLETED]

https://ssiw.qvalent.com 

(Production Environment)

Monday 6th June 2022 @ 10:00am AEST

[COMPLETED]

https://ccapi.client.qvalent.com

(Production Environment)

Monday 4th July @ 10:00am AEST

Customers however can take action now to prepare for these changes.

What certificates are being changed?

Qvalent will begin to issue server certificates for the above hosts from the following Root and Intermediate Certificates

Root Certificate

Common Name (CN)

Entrust Root Certification Authority - G2

Valid Until

8/12/2030

Thumbprint

8c f4 27 fd 79 0c 3a d1 66 06 8d e8 1e 57 ef bb 93 22 72 d4

Available from Entrust at

https://entrust.com/root-certificates/entrust_g2_ca.cer

Intermediate Certificate

Common Name (CN)

Entrust Certification Authority - L1K

Issued By

Entrust Root Certification Authority - G2

Valid Until

6/12/2030

Thumbprint

f2 1c 12 f4 6c db 6b 2e 16 f0 9f 94 19 cd ff 32 84 37 b2 d7

Available from Entrust at

https://entrust.com/root-certificates/entrust_l1k.cer

How does this change affect my application?

When your application connects to one of the above hosts, it requests it validates the certificate issued to these hosts comes from a trusted certificate authority.

If you do not have the new Entrust root certificate authority hosts in your repository, then your application will not trust the Qvalent host.

If this happens, your application will not connect to our web service, which will result in a loss of banking service.

What must I do?

To Do

To Do

1

Read this detailed change advice and ensure it reaches all application owners which connect to Qvalent services to investigate the impact of this change.

2

Identify all applications which interact with these hosts and take action to prepare for this change immediately.

3

Validate preparedness of applications and systems for this change by ensuring all systems have the Entrust Root CA in their application’s trust store.

4

Take immediate action to add the Entrust Root CA to your application's trust store if it is not present.

  • This procedure varies depending on your application technology.

  • For QuickStream / PayWay / QuickSuper / iLink customers using https://ccapi.client.qvalent.com, https://ws.qvalent.com or https://ssiw.qvalent.com perform UAT testing against our test environment to ensure these changes are appropriate for your application and ensure changes are promoted to Production environments. Our test environment already has the new Entrust certificates installed.

5

Understand and be prepared to instigate business BCP processes in the event of any issues post change to ensure banking services continue with this loss of service

6

Understand and be prepared to gather application developer and systems administrator resources in the event of any issues post change.

Test Environment

Below is a list of the corresponding Test URLs. These URLs have Entrust certificates which you can use to confirm your integration.

Product