FHIR Chat · docs / Issue #17 How should stand-alone launch apps authe... · fhircast-github

Stream: fhircast-github

Topic: docs / Issue #17 How should stand-alone launch apps authe...


view this post on Zulip Github Notifications (FHIRcast) (Aug 07 2018 at 20:47):

isaacvetter commented on Issue #17

Hey @jeremysrichardson ,

I think that this is closely related to #4 , see the resolution to that issue and the spec's Launch Scenario's page.

I had initially tried to also fit Backend services into FHIRcast as a third launching mechanism, but got held up on this conversation. (tldr; backend services doesn't have a user, we necesssarily do).

I _think_ this resolves, this particular issue, will you re-open if you disagree?

Isaac

view this post on Zulip Github Notifications (FHIRcast) (Aug 07 2018 at 20:47):

isaacvetter closed Issue #17(assigned to isaacvetter)

I spoke with a few people to try to get my head around how authentication would work for stand-alone apps. I spoke with Isaac, and he thought it might be more appropriate to use the back-end services model for SMART over OAuth2.

http://docs.smarthealthit.org/authorization/backend-services/


Last updated: Apr 12 2022 at 19:14 UTC