You can find more info on getting the User-Auth_Token at http://healthblog.vitraag.com/2008/06/doing-user-authentication-with-healthvault/

Hope this helps.

regards,
Vaibhav

I figured out the problem. The xml tag name should be in lowercase instead of uppercase.

It successfully CreateAuthenticatedSessionToken when i send your CreateAuthenticatedSessionToken xml request.

However, when i send your GetPersonInfo xml request, it responsed, ”
11Access is denied.”

Then I changed the auth-token and used the new generated one while everything else remains the same. I send the new GetPersonInfo xml request and it responded:

7The credential token has expired.

I suppose the User-Auth-Token has expired. But how do we get the User-Auth-Token?

Thanks!
Your help will be greatly appreciated.

I send your xml to https://platform.healthvault-ppe.com/platform/wildcat.ashx

but it shows me an “500″ error message:

Runtime Error

body {font-family:”Verdana”;font-weight:normal;font-size: .7em;color:black;}
p {font-family:”Verdana”;font-weight:normal;color:black;margin-top: -5px}
b {font-family:”Verdana”;font-weight:bold;color:black;margin-top: -5px}
H1 { font-family:”Verdana”;font-weight:normal;font-size:18pt;color:red }
H2 { font-family:”Verdana”;font-weight:normal;font-size:14pt;color:maroon }
pre {font-family:”Lucida Console”;font-size: .9em}
.marker {font-weight: bold; color: black;text-decoration: none;}
.version {color: gray;}
.error {margin-bottom: 10px;}
.expandable { text-decoration:underline; font-weight:bold; color:navy; cursor:hand; }

Server Error in ‘/platform’ Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application’s <customErrors> configuration tag to point to a custom error page URL.

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>

Thanks!!