Wednesday, November 14, 2012 5:09 AMHello,everyone.
Some documents about SODA have written that the HealthVault .Net SDK's SODA APIs can create a new public and private key and add it to the current user’s certificate store for app authentication and the establishing process of the client sample in SDK is really like that.
But when I read the document of "HealthVault Mobile"(link:http://msdn.microsoft.com/en-us/library/hh567903.aspx),the process of establishing a connection on a mobile device is different from the desktop soda app. The step 2 is that "Application obtains a new application identifier, shared secret, and app creation token by calling the HealthVault web service and passing in the master application identifier,)".
So my question is why the app of mobile don't use public and private key for authentication.And what is the distinction between certificate for desktop app and shared secret and app creation token for mobile device.
Any help would be grateful.
- Edited by Kevin00000000 Wednesday, November 14, 2012 5:10 AM
Wednesday, November 14, 2012 6:42 AM
Mobile soda was created because for mobile devices because some platforms did not allow us to be able to create certificates and store these certificates into the cert store like how a desktop SODA application. The preferred and simpler method for doing any sort of SODA application would be to use the mobile SODA process.
- Marked As Answer by Kevin00000000 Wednesday, November 21, 2012 8:05 AM