The explanation, so far, for Experian’s required upgrade allowing only TLS version 1.2 for connections to the Demo Environment (and Production after customers test in Demo).
- On the 8th of the month, Experian was supposed to only allow TLS 1.2
- My software ran fine
- The following Monday, I called to ensure they made the changes and then emailed a few times. No one could confirm.
- On the 19th, I started getting emails that customers couldn’t connect to the Demo environment.
- Easy Access will indeed need to be updated before you can use Demo
- On the 19th, I got a new bulletin from Experian stating that 12 midnight, July 20th, they will allow TLS 1.1 again since so many people were having problems, and they did and demo now works with Easy Access but now I know I have to update the TLS in Easy Access.
- Experian stated in the next 2 to 3 weeks they will re-implement TLS 1.2 (will see)
- Either way, I am adding support for TLS 1.2 but really won’t be able to confirm it indeed works until the switch over.
- Now Experian is talking about keeping TLS 1.1 and 1.2 active for a while longer but creating a new Demo URL for people who want to test. This way, the software currently in the field will continue to run and vendor like me can test our changes against the new URL.
- Either way, TLS is comming, first to the Demo Environment and latter to the Production Environment.
- What I know now is that anyone who uses Easy Access to pull Experian reports will have to update when I complete the update.
I will keep this post updated, changing the date of the post each time so that those who subscribe to my blog will not be kept in the dark.
Hope this keeps you up to date.