Don’t risk connectivity failures: The data center migration will happen on August 18, 2024, and traffic is being routed to the new data center now. If you haven’t already, you must finish preparing for the transition by implementing the required changes to your Production environment. You will experience connectivity failures as we continue to transition traffic to the new data center if your updates have not been made.

Please contact us with questions or concerns, bookmark this page and check back often for updates.

Testing Instructions

This section contains technical details regarding secure connections between our clients. Please share this page with the appropriate teams within your organization.

We will perform a complete DNS switchover to point to the New Data Center on the targeted dates in UAT (June 3, 2024) and Production (August 18, 2024).

Please refer to the testing window for respective environments.

UAT PROD
May 1, 2024 – May 31, 2024  June 1, 2024 – July 31, 2024

If you have IP restrictions setup and missed the testing phase, you will start to experience connectivity errors caused by your own firewall rules, IP allow-list or similar setup at your end.

What’s Happening?

Ahead of the migration, self-service connectivity testing will be available in both our User Acceptance Testing (UAT) and Production (PROD) environments. Only connectivity testing is required for this move. All current existing API endpoints (DNS and URL) will remain unchanged and be functioning as BAU without any outages or disruptions during the move.

Clients will be provided with two options to test connectivity:

  • Initiating an API Call (Recommended): Test the endpoint using existing credentials and validate the connectivity by receiving a successful response of ‘HTTP 200’ Status code.
UAT PROD

MTLS:

https://api-mtls-gw03-uat.jpmchase.com/tsapi/v1/connect

MTLS:

https://api-mtls-gw03.jpmchase.com/tsapi/v1/connect

OAuth:

https://api-oauth-gw03-uat.jpmchase.com/tsapi/v1/connect

OAuth:

https://api-apps-gw03.jpmchase.com/tsapi/v1/connect

PCI-MTLS:

https://api-mtls-gw03-var-pci.jpmchase.com/tsapi/v1/connect

PCI-MTLS:

https://api-mtls-gw03-pci.jpmchase.com/tsapi/v1/connect

  • Network cURL Test: Conducting a network cURL test in UAT and PROD environments from the system that currently accesses J.P. Morgan’s APIs. For instructions on network cURL testing, please refer to the steps below:

1. Download the cURL tool and ensure the correct installation for your platform.

2. Use the following commands to test across each environment:

For testing Mutual TLS connectivity

UAT: cURL " https://api-mtls-gw03-uat.jpmchase.com/tsapi/v1/connect “-X GET --header "Accept:application/json" --cert Transport_UAT_Cert.crt (replace with exact certificate name) --key Transport_UAT.key.pem(replace with exact certificate name)

PROD: cURL " https://api-mtls-gw03.jpmchase.com/tsapi/v1/connect "-X GET --header "Accept: application/json" --certTransport_PROD_Cert.crt (replace with exact certificate name) --key Transport_PROD.key.pem(replace with exact certificate name)

For testing OAuth connectivity

UAT: cURL" https://api-oauth-gw03-uat.jpmchase.com/tsapi/vl/connect"-X GET--header "Accept:application/json" -X GET --header "Authorization: Bearer<token>"

PROD: cURL " https://api-apps-gw03.jpmchase.com/tsapi/v1/connect "-X GET --header "Accept: application/json" -X GET --header"Authorization: Bearer <token>"

3. Confirm successful connection to the new Data Center by emailing api.connectivity.testing@jpmchase.com including your Access Profile ID in the subject of the email and attaching a screenshot of connection validation.

Sample Success Response:
* using HTTP/1.x
> GET /tsapi/v1/connect HTTP/1.1
> Host:  api-mtls-gw03-uat.jpmchase.com/tsapi/v1/connect
> User-Agent: curl/8.1.2
> Accept: application/json

< HTTP/1.1 200 OK
< Date: Fri, 05 Jan 2024 19:25:21 GMT
< Content-Type: application/json
< Connection: keep-alive
< Strict-Transport-Security:max-age=63072000; includeSubdomains; preload
< X-Frame-Options: SAMEORIGIN
< X-Content-Type-Options: nosniff
< X-XSS-Protection: 1; mode=block
< Vary: Accept-Encoding
< Transfer-Encoding: chunked
< Set-Cookie:ppnet_443=!
0rZVIjwugCYIJ4Sb6a6YvQ00svN1q6IU4xbzs5skJDTiG4Y4GFhrD0GPzYJLk1E4ybIUrTxDP6pHYg==;path=/; Httponly; Secure

{"status": “Success”,“Environment”: “UAT”}

To ensure technical specifications and guidance remains accurate, please do not translate this page into any other language.

Support

We’ve set up a support team to help you with any migration questions you may have. If you need help, please call us on +1 (877) 827-5921. Our team is available to answer your questions, in your time zone, Monday through Friday, 8 a.m. to 6 p.m. You can also email us at jpmc.datacenter.migrations@jpmchase.com.

Our helpline will support the following languages: English, Spanish, Japanese and Mandarin.