I'm new to ACS, WIF, and federated identity stuff in general, but I've been working through examples in the WIF SDK training kit (and the ACS samples, as well), but I'm having an issue talking to an ASP.NET MVC WebAPI-based REST service (hosted on Azure) where I set up ACS as the FP. If I use my browser to test out my REST service (http://jordan-helloacs.cloudapp.net), I get the traditional "passive authentication" experience and can log in via Live ID or Google (which I set up as the two IP's in ACS).
However, I'm trying to achieve a "passive-active" experience with a simple WPF application that retrieves the available IP's by using the
"https://[myACSnamespace].accesscontrol.windows.net/v2/metadata/IdentityProviders.js?protocol=javascriptnotify&realm=http://jordan-helloacs.cloudapp.net/&version=1.0",
endpoint on ACS to list the available IP's, and then hosts a WebBrowser control to handle the login to that IP, and extracts the ACS token that is returned from ACS, and then (using RestSharp) makes a GET call to my endpoint at http://jordan-helloacs.cloudapp.net. I've successfully extracted the token (I've tried both SWT and SAML2), but I cannot figure out what I need to do with the token once I've got it from the WebBrowser control. I've seen several different examples where the token is prepended with either "OAUTH" or "WRAP access_token=" and just passed in the "Authorization" header, but nothing I'm doing seems to be working. My RestSharp client just keeps getting 302'd to the ACS sign in page.
Any tips on what I might be doing wrong? How do I know how to specify the auth header format?