http://blogs.msdn.com/b/card/archive/2010/01/27/customizing-the-ad-fs-2-0-sign-in-web-pages.aspxWhat do the following three questions in the AD FS 2.0 forums have in common? · Reducing default steps in Sign-In process and changing default look &amp; feel in Sign-In process in Geneva server · How to authenticate a non-Active Directory useren-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.msdn.com/b/card/archive/2010/01/27/customizing-the-ad-fs-2-0-sign-in-web-pages.aspx#10238227Thu, 17 Nov 2011 18:29:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:10238227Martin Bélanger<p>With this solution, the SSO doesn&#39;t work.</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10238227" width="1" height="1">http://blogs.msdn.com/b/card/archive/2010/01/27/customizing-the-ad-fs-2-0-sign-in-web-pages.aspx#10061691Tue, 14 Sep 2010 12:56:31 GMT91d46819-8472-40ad-a661-2c78acb4018c:10061691Catalin Pop<p>This sample doesn&#39;t work, for some reason I&#39;ve tried with multiple custom STS&#39;es and with &quot;<a rel="nofollow" target="_new" href="https://ipsts.federatedidentity.net/SecurityTokenService/InteropSts.svc/Sts&quot;">ipsts.federatedidentity.net/.../Sts&quot;</a> and the result is the same: &quot;http 500 Internal Server Error&quot;.</p> <p>Any ideeas what&#39;s happening?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=10061691" width="1" height="1">http://blogs.msdn.com/b/card/archive/2010/01/27/customizing-the-ad-fs-2-0-sign-in-web-pages.aspx#9979699Tue, 16 Mar 2010 18:03:01 GMT91d46819-8472-40ad-a661-2c78acb4018c:9979699busta<p>For authenticating users against a non-AD credential store, calling a custom STS is an &quot;ok&quot; workaround. However, if I have to create a custom STS to authenticate users against a non-AD credential store, then in many cases I may not both with ADFS V2 at all. Why pay the price for another STS bounce? By the time I create the custom STS I can authenticate the user and issue the SAML token carrying appropriate claims in a single call. Insetad I might create a custom RP-STS, federate with ADFS V2 for my windows domain users, and then use the RP-STS as the domain for non-AD users. </p> <p>What I really wish for is a way to have a sign-in or RST to ADFS V2 look at a different credential store behind the scenes without bouncing to another STS. Is there a roadmap for this?</p> <div style="clear:both;"></div><img src="http://blogs.msdn.com/aggbug.aspx?PostID=9979699" width="1" height="1">