Unanswered AppAuth Problem

All Replies

  • Wednesday, January 18, 2012 4:03 PM
     
     
    If all you see is a blank page, it may be that a 500 error occurred.  Do you see any activity either within a Fiddler Trace or Network trace that would indicate that account.healthvault.com actually sent a response?
    Adam W. Saxton | Microsoft HSG Escalation Services | http://twitter.com/awsaxton
  • Wednesday, January 18, 2012 10:20 PM
     
     
    All I see in Fiddler is a CONNECT to wtsdc.healthvault.com:443 with a 200 Result
  • Wednesday, January 18, 2012 11:00 PM
     
     

    also seeing the following error when doing a CREATEACCOUNT with eprep=true

     

    We're sorry. We could not complete your last request.

    An error occurred that we did not expect. The most recent action you were taking may not have completed successfully, but the rest of your HealthVault information is still safe.

  • Friday, January 20, 2012 12:50 AM
    Owner
     
     
    What URL are you using to launch the CREATEACOUNT target with ePrep=true. Can you try this URL: https://account.healthvault.com/redirect.aspx?target=createaccount&targetqs=eprep%3dtrue 
  • Friday, January 20, 2012 5:38 PM
     
     
    i use page.RedirectToShellUrl("CREATEACCOUNT", "appid=xxxx" + "&eprep=true")
  • Friday, January 20, 2012 6:32 PM
     
     
    Just to clarify - the error page when using create account target, you see that when using any browser? And when doing app auth, you only see it fail on Chrome?  Is that correct?  Also when doing app auth, you should never directly hit the app auth page, you should hit it with the APPAUTH target. The blank page in Chrome looks like an issue with cookies not being set properly so our server didn't know where to redirect you.
  • Friday, January 20, 2012 7:16 PM
     
     

    to simplify ... let's ignore the CREATEACCOUNT error for now. I think that is unrelated. I believe now that was related to a HV account being deleted and then trying to create it again.

     

    In terms of the APPAUTH yes it seems to be related just to Chrome (running version: 16.0.912.75 m). This is production code that has been working for more than a year.

     

    We redirect using RedirecToShell:  page.RedirectToShellUrl("APPAUTH", "appid=xxxx");

  • Friday, June 29, 2012 2:23 PM
     
     
    Curious if you have found the solution to your problem.
  • Monday, July 02, 2012 6:53 PM
     
     
    Joshua are you seeing issues now? If so, can you post the URL you are hitting HV and what browser you are using that is coming up with a blank page?
  • Thursday, July 05, 2012 12:32 PM
     
     
    Yes this has been resolved. Sorry for the delay.