大网数据广告活动
域与目录服务

AD FS Troubleshooting - Fiddler - WS-Federation

· 52CE 我爱测

This document shows an in-depth trace of a WS-Federation exchange with AD FS

AD FS and Windows Server Federation diagram

Step 1 and 2

This is the beginning of our trace. In this frame we see the following:

Start of Fiddler trace

Request:

  • HTTP GET to our relying party (https://sql1.contoso.com/SampApp)

Response:

  • The Response is a HTTP 302 (Redirect). The Transport data in the Response header shows where to redirect to (https://sts.contoso.com/adfs/ls)
  • The redirect URL contains wa=wsignin 1.0 which tells us that our RP application has built a WS-Federation sign-in request for us and sent this to the AD FS's /adfs/ls/ endpoint. This is known as Redirect binding.

Transport data in the Response header

Step 3 and 4

Continuation Fiddler trace

Request:

  • HTTP GET to our AD FS server(sts.contoso.com)

Response:

  • The Response is a prompt for credentials. This indicates that we are using forms authentication
  • By clicking on the WebView of the Response you can see the credentials prompt.

Screenshot of the web view of the response showing the credentials prompt.

Step 5 and 6

WebView tab of the prompt for credentials Prompt screen

Request:

  • HTTP POST with our username and password.
  • We present our credentials. By looking at the Raw data in the request we can see the credentials

Response:

  • The response is Found and the MSIAuth encrypted cookie is created and returned. This is used to validate the SAML assertion produced by our client. This is also known as the "authentication cookie" and will only be present when AD FS is the Idp.

Step 7 and 8

Screenshot of the of Fiddler trace showing the H T T P Get request and the response to that request.

Request:

  • Now that we have authenticated we do another HTTP GET to the AD FS server and present our authentication token

Response:

  • The response is an HTTP OK which means that AD FS has authenticated the user based on the credentials provided
  • Also, we set 3 cookies back to the client
    • MSISAuthenticated contains a base64-encoded timestamp value for when the client was authenticated.
    • MSISLoopDetectionCookie is used by the AD FS infinite loop detection mechanism to stop clients who have ended up in an infinite redirection loop to the Federation Server. The cookie data is a timestamp that is base64 encoded.
    • MSISSignout is used to keep track of the IdP and all RPs visited for the SSO session. This cookie is utilized when a WS-Federation sign-out is invoked. You can see the contents of this cookie using a base64 decoder.

Step 9 and 10

Screenshot of the of Fiddler trace showing the H T T P Post request and the response to that request.

Request:

  • HTTP POST

Response:

  • The response is a Found

Step 11 and 12

Finalization of Fiddler trace

Request:

  • HTTP GET

Response:

  • The response is OK

Next Steps

Source: Microsoft Learn / Windows Server documentation by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / Windows Server documentation
适用范围
Windows Server · Source date 02/13/2024
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。