Understanding the view of the Fiddler tool
Configure AD FS 2.0 to allow Fiddler to act as a man-in-the-middle to the HTTPS session
If AD FS 2.0 is the claims provider (identity provider, meaning, you are authenticating to the AD FS 2.0 server) and is configured to utilize Windows authentication, we need to disable Extended Protection for Authentication on the AD FS 2.0 server in order for Fiddler to be able to act as a man-in-the-middle to the HTTPS session. Follow the steps in the following article to disable Extended Protection for Authentication: AD FS 2.0: Continuously Prompted for Credentials While Using Fiddler Web Debugger
Capture the WS-Federation sign-in data
We will be capturing the trace data from the client machine
Analyze the captured WS-Federation sign-in data
This section is a work in progress.
Thanks you, v useful, could you post a blog about WIF and 2 different custom STS (in form, and in windows authentification). I met a problem with RP after the STS authentificated and after RP set the authentification cookies, the browser doesn't send again these cookie when trying to get the default page, so WIF redirects again and again tries to set these cookies, then comes back to default page, and so on it loops that way forever like the authentification cookies were not set or not sent.... Could you help?