Using Fiddler for capturing traffic between Enterprise Tester and 3rd party applications
Before you start, Important Notes:
- It is best to do this outside of working hours as it can disrupt / halt traffic between Enterprise Tester and the external system.
- After changing the web.config file as directed in the steps below please be aware that NOT having Fiddler turned on will mean traffic between the two applications will stop. You must comment out or delete the lines added in the instructions below when you are finished.
- When HTTPS decryption is turned on, you may receive a 'loading config data failed' error.
This may be due to the "External System"configuration in Enterprise Tester.
There is an "ignore invalid certificates" option which needs to be ticked, otherwise it refuses to connect based on the fact it sees the intercepting fiddler certificate as invalid
- Download "Fiddler for .NET 4" from here: http://www.telerik.com/download/Fiddler
- Install Fiddler on the Enterprise Tester Application Server.
- Start Fiddler.
- Enable "Decrypt HTTPS traffic", you will be prompted to install/trust a local self-signed certificate, you must do this for SSL decryption to work correctly.
To do this navigate to Fiddler Options from the Tools menu.
Then from the HTTPS tab select Decrypt HTTPS traffic.
- Start a Fiddler Capture.
- Add a new section your Enterprise Tester installations web.config file - place the fragment just before the closing </configuration> tag at the bottom of the web.config file.
The fragment should look like this:
<proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://localhost:8888" usesystemdefault="false" />
- Initiate a sync between Enterprise Tester and the third party application and leave it running until you capture the necessary data.
All the requests between Enterprise Tester and the application will be captured.
Note: Sometimes you can see the data is not being captured, in this case please stop and then restart the capture within Fiddler.
- Now stop the capture and select to save all sessions as a .SAZ file.
- Email this file through to us.
- To stop the traffic redirect, comment out or remove the fragment added to the web.config file in Step 6.
Save your web.config file.