Running a HealthVault Application in IIS without installing a certificate in the certificate store

Starting with the HealthVault 0908 SDK release, HealthVault applications can run with an application’s certificate stored in a file store instead of in a certificate store by setting the ApplicationCertificateFileName key and its value in the web.config file. We often noticed that the developers facing issues in Windows Server 2008 R2 and Windows 7 machines…

0

Creating your own ApplicationId and certificates

The Microsoft HealthVault SDK comes with a few sample applications and ApplicationIds which you can use in order to explore the platform and even to get started on your own application.  But at some point in your application development process, you will want to customize your ApplicationName and Logo.  You may also want to use…

0

More About Certificate Errors

Here is some help on diagnosing some of the common modes of failure with HealthVault certificate management. Access denied The most common cause of this error is that the application can find the certificate but the account running the app does not have the proper permissions to utilize its private key at run-time.  See the…

0

Certificate Errors

Got a good question today from a long-time HealthVault Developer — at least they are long-time in terms of the short history of HealthVault. If your application certificate is not configured correctly, either on your app server or on the HealthVault server, the first time that you will see an error is the first time…

0

Certificate Management

We get a lot of questions about managing your HealthVault application certificate.  When your application initiates a connection to HealthVault, it uses its unique private key to encrypt the first handshake message that it sends.  HealthVault then uses a public key to verify that the sender of this message is indeed a trusted host.  This…

0