Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ballot#154 Joshua Mandel, Boston Children's Hospital | @https://github.com/smart-on-fhir/smart-on-fhir.github.io/issues/146 | From: client-side app... #151

Closed
jmandel opened this issue Dec 21, 2017 · 1 comment

Comments

@jmandel
Copy link
Collaborator

jmandel commented Dec 21, 2017

Ballot Weight

NEG

Where

:: http://www.hl7.org/fhir/smart-app-launch/

What

Joshua Mandel, Boston Children's Hospital
@smart-on-fhir/smart-on-fhir.github.io#146
From: client-side apps (for example, HTML5/JS browser-based apps, iOS mobile apps, or Windows desktop apps) can provide adequate security � but they can�t �keep a secret� in the OAuth2 sense. That is to say, any �secret� key, code, or string that�s embedded in the app can potentially be extracted by an end-user or attacker. So security for these apps can�t depend on secrets embedded at install-time.

Josh's Triage Notes

Theme: "Where confidential apps can run"

Disposition

Accept changes proposed in https://github.com/HL7/smart-app-launch/pull/1/files?short_path=d680e8a#diff-d680e8a854a7cbad6d490c445cba2eba .

This provides references to Public vs Confidentail client definitions in the OAuth 2.0 spec and clarifies that our assessment is advice ("should") rather than a strict requirement ("shall").

Vote Details

Pro-Con-Abstain: 10-0-1
Date: 2017-09-14

@Healthedata1
Copy link
Collaborator

See #1 for proposed disposition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants