http://blogs.msdn.com/govindr/archive/tags/ADFS/default.aspxTags: ADFSenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/govindr/archive/2007/02/19/ws-federation-passive.aspxMon, 19 Feb 2007 21:57:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:1717949govindr0http://blogs.msdn.com/govindr/comments/1717949.aspxhttp://blogs.msdn.com/govindr/commentrss.aspx?PostID=1717949<P>I have discussed about <a href="http://blogs.msdn.com/govindr/archive/2006/10/18/federation.aspx">Federation</a> before. This post discusses Federation from the active context. "Active" means that&nbsp;the client is a smart client capable of doing encryption and signing and can actively participate in the Federation protocol. There are cases where the client is simply a Web Browser that is not capable of creating a secure message. In these cases the client is said to be "Passive". Federation in this case can be regulated through a series of HTTP 302 web redirects. The profile is described as the <A class="" href="http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-fedpass/ws-fedpass.pdf" target=_blank mce_href="http://download.boulder.ibm.com/ibmdl/pub/software/dw/specs/ws-fedpass/ws-fedpass.pdf">WS-Federation Passive</A> profile.</P> <P>ADFS Version 1 uses this profile to enable Federation of Identity. Moving forward ADFS will have support for Active and Passive profiles from version 2 onwards.</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=1717949" width="1" height="1">SecurityFederationwebservicesADFS