Using WMC with no web interface, entirely within a client app?

Question

I have a client application that communicates with a hosted server, where the server provides services specific to a user.  Rather than have my own set of accounts, I would like the user to be able to log into their Windows Live account, and I would key my per-user server resources to the CID.

 

The trick here is, I'm not running in a web page, nor can I direct users to a browser or even a hosted IE control.  I will implement the sign-in "form" entirely within my own client application's UI.  Ideally, they type their username and password into the user interface in my client app, and my client app would then send the log-in information to Windows Live.

 

Is this scenario enabled by Windows Messenger Connect?  If so, I don't see how.  While there is a "desktop application" application type, there is no information on MSDN about how to implement Windows Live sign-in and profile services without using a user-facing website.  If not, is there another supported set of Windows Live technology that enables this scenario?

 

As an aside, I can use .NET if necessary, but I would rather work with a purely REST interface so I can implement in non-.NET languages.

---

Matthew Picioccio, XNA

Answer 1

This kind of feature used to be provided in the Windows Live ID Client SDK, from 2008.  However, the documentation all indicates that this technology is deprecated, in favor of Windows Messenger Connect.  I can see that Windows Messenger Connect supports a "desktop application" application type, but I can't find any information on how to use WMC without implementing a website, website redirects, etc. (I just want to access WLID as a service).

 

Windows Identity Foundation also provides an interesting system, but that doesn't seem to interact with Windows Live ID.  I would use WIF if I wanted to create a client desktop application that interacted with my own set of user profiles, but in this case, I really want to leverage Windows Live IDs (so I don't have to reimplement the wheel).

---

Matthew Picioccio

Answer 2

Choosing "Windows application" on Messenger Connect will require you to host a WebBrowser control in your application. According to http://msdn.microsoft.com/en-us/library/ff749771.aspx , you can get the verification code after consent as the page title.

Implementing a sign-in form by yourself is not supported, because you will be able to fetch user's password.

Answer 3

Okay, that's what I was afraid of.  I'll just have to jettison Windows Live ID, and either go to another common-ID system or just bite the bullet and roll my own set of profiles.

---

Matthew Picioccio