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 that your application tries to read or write data to/from the HealthVault platform.  This means that your end users (or more likely your test accounts) can successfully go through Application Authorization before they will see this error.

The fact that you get through App AuthZ without seeing any errors may lead you to believe that your certificate must be correct, but that is not the case.  If you see an "Access Denies" error the first time that you try to load a page containing health information, then the most likely cause of your issue is an improperly configured application certificate. 

See the post linked above for more information on certificate management.