Warning
WARNING: The TrackAbout MetaWiki has been deprecated and is no longer being updated.

Please visit our new TrackAbout Knowledge Base at https://supportkb.trackabout.com for the most-up-to-date documentation on TrackAbout and TrackAbout Mobile.

TLS 1.2 Test Environment Testing

From TrackAbout MetaWiki
Revision as of 12:05, 4 March 2020 by Lsilverman (talk | contribs) (update (by SublimeText.Mediawiker))
Jump to navigation Jump to search

TLS 1.2 Test Environment Testing

These tests are intended for basic testing of TLS 1.2 connectivity during the 24-hour test windows scheduled.

Mar-24 - Test Environment - First 24-Hour Test

We shall perform a 24-hour change to our customer-facing Test Environment (test.trackabout.com) on Tuesday, March 24th, 2020 at 10:00 AM Eastern US Time.


Most customers do not have dedicated Test environments. This is generally reserved for our largest customers and ERP vendor partners so they may test ERP integrations.


We are creating a shared instance specifically for TLS 1.2 testing. Details below.

Mar-31 - Test Environment - Second 24-Hour Test

We shall perform a second 24-hour change to the Test Environment on Tuesday, March 31st, 2020 at 10:00 AM Eastern US Time.

Apr-21 - Test Environment - Permanent Change

The customer-facing test environment (test.trackabout.com) change shall be made permanent on Tuesday, April 21st, 2020 at 10:00 AM Eastern US Time.

After the TLS 1.2 changes are made permanent, this TrackAbout instance will be deleted.

Test Site Details

URL: https://test.trackabout.com
Username: tls_test
Password: lvD7IB2!L#Zw
TAMobile 6 Sync Key: NLSR2US5MS32

You may need to have "test.trackabout.com" added to a network firewall allow-list or white-list before you may access it the first time.

Important!

With multiple users using the same username and password, it's possible that someone else testing will cause you to get logged out of the web site, TAMobile 6 or TAMobile 7 on iOS or Android.

This is by security design. One user should not be logged into multiple smartphones, devices, etc, at the same time. However, it may hamper your testing slightly.

You do not need to stay logged into these environments for very long to test TLS 1.2 connectivity. If you should get forcibly logged out before testing to your satisfaction, simply try again.

Test Environment - Web Browser Test

Use the credentials provided to log into https://test.trackabout.com

Upon login, you should see the following:

Test-environment.png

If you see this page, the test is successful. You may now log out.

If not, your browser test has failed.

  • Make sure you are using the most up-to-date version of your web browser.
  • Also make sure your computer is up-to-date on operating system updates.

Test Environment - Basic ERP REST API Test

From your ERP or other system, make an HTTP GET request to https://test.trackabout.com/api/heartbeat

The GET request should return HTTP status 200 and HTTP body of "0".

Anything else is a failure.

Test Environment - TAMobile 6 Full Test

Please follow the same instructions as outlined in TLS 1.2 QA Environment Testing, with these differences:

Your TAMobile 6 config.ini should look like this:

[Config]
SyncUrl = https://test.trackabout.com/
SyncKey = NLSR2US5MS32
SyncPort = 443

You will be prompted to pair your device upon your first sync attempt.

Log into the web site using the username and password provided above.

If you can even get to the device pairing test, you have succeeded in testing TLS 1.2.

Test Environment - Android and iOS Test

If you are signed into the smartphone TrackAbout app, log out.

On the login screen, click the Settings link.

In Settings, for Environment, select Test.

Back on the login screen, use the tls_test username and provided password to log in.

If you fail to sync, try a few times as others might also be trying at the same time.

If you get even a single successful sync and end up on the TLS Test screen with a single "Wireless Lookup" button, you have succeeded.