You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sandbox code sets the expires_in based on the expires_in smart launch token response but looks like HSPC is not sending expires_in value when launching sandbox as SOF app. Not sure if this is the right place to post this given this is related to HSPC sandbox. But also wondering if the sandbox code should catch this
The text was updated successfully, but these errors were encountered:
@yashaskram - Jacob over at HSPC was fantastic and deployed a change to their authorization server and now the expires_in field is being returned. I've confirmed this in the CDS Hooks Sandbox as well.
We can leave this issue open as I agree with you that it would be good for us to put in some validation to ensure that the expires_in field is always set.
When launching sandbox app through HSPC, fhirAuthorization populates fine but missing expires_in field.
The sandbox code sets the expires_in based on the expires_in smart launch token response but looks like HSPC is not sending expires_in value when launching sandbox as SOF app. Not sure if this is the right place to post this given this is related to HSPC sandbox. But also wondering if the sandbox code should catch this
The text was updated successfully, but these errors were encountered: