Yes, It is not a great idea and I don't like it either. But that is what the Microsoft HealthVault requires. The application has to generate a key pair when trying to authenticate for the first time or later when we do not have an access token. Here are more details in this pdf in case you want to look.
http://www.google.com/url?sa=t&source=web&cd=1&ved=0CBkQFjAA&url=http://download.microsoft.com/download/0/4/9/0498cecf-d0b1-4a72-b9b7-17eb7d7ada98/Connecting_Rich_Client_Apps.pdf&rct=j&q=healthvault%20soda%20client%20pdf&ei=nuzmTJOPMIaglAf8_OCiDA&usg=AFQjCNGlBRZmUeNvspxNx7mQxvY9gtR9Aw&sig2=8tbscPDpIRfTklM82uQSrQ Thank you On Nov 19, 9:49 am, Marcin Orlowski <webnet.andr...@gmail.com> wrote: > On 19 November 2010 17:23, Achie <krishna.acha...@gmail.com> wrote: > > > In that example the user is using Keytool to create the certificate > > and then transferring the keystore to the mobile. > > What I want is that my application to create the keystore and > > certificate on the device and then use them. > > Generating certificate on device does not look like sane idea in > most cases as i.e. pkey shall be created there as well. What > you really want to achieve? -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
