Weavor,
I'm still working to get an official response for you, but I believe the answer will be that the LiveID SDK doesn't support what you're trying to do, trying to bring multiple browser sessions under one LiveID client app umbrella. I'm not sure that the LiveID SDK tokens generated for the stand alone client app can affect or apply to the browser sessions (since browser sessions don't affect each other either).
-Danny
Weavor, you mention that you are using the "Live ID SDK", could you be more specific What SDK are you using If you are using the Client SDK, you can use the OpenAuthenticatedBrowser() method to open a pre-authenticated browser window to a Windows Live Service website. If you can provide a little more information I may be able to help you, or point you to someone who can.
Thanks,
Weavor, have you looked at the GetNavigationData() method OpenAuthenticatedBrowser() as you pointed out simply opens a new instance of the default browser, and is only compatible with stand-alone IE6+. The GetNavigationData() method is there to support other scenarios. Here is a quote from the SDK topic "Opening An Authenticated Browser Window":
To open an authenticated browser using browsers other than Internet Explorer requires your application to invoke the execution of whatever browser is installed on the end user's computer. Additionally, you must ensure that the browser sends the appropriate authentication data in a form post to the appropriate Windows Live ID site or service URL. For more information or to obtain service-specific URLs, see the documentation for that service.
How you implement these features will vary depending on the exact configuration of the end-user's computer. The authentication data that the Web service requires can be obtained by calling the GetNavigationData method.
Would it be possible to use a similar method to authenticate embedded browser controls If you try this, please let me know the outcome.