Stream: fhircast-github
Topic: fhircast-docs / Issue #91 May 2019 Ballot Comment: Is OID...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #91
## May 2019 Ballot Comment: Is OIDC support required?
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-Q ClarificationSummary: Is OIDC support required?
Comment: Does FHIRcast require the SMART server to support OIDC? Currently, there's no explicit requirement and SMART itself doesn't exactly require it.
Existing wording: Per SMART, when scopes of openid and fhirUser are granted, the app will additionally receive the current user's identity in an id_token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot labeled Issue #91
## May 2019 Ballot Comment: Is OIDC support required?
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-Q ClarificationSummary: Is OIDC support required?
Comment: Does FHIRcast require the SMART server to support OIDC? Currently, there's no explicit requirement and SMART itself doesn't exactly require it.
Existing wording: Per SMART, when scopes of openid and fhirUser are granted, the app will additionally receive the current user's identity in an id_token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot edited Issue #91
## May 2019 Ballot Comment: Is OIDC support required?
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-Q ClarificationSummary: Is OIDC support required?
Comment: Does FHIRcast require the SMART server to support OIDC? Currently, there's no explicit requirement and SMART itself doesn't exactly require it.
Existing wording: Per SMART, when scopes of openid and fhirUser are granted, the app will additionally receive the current user's identity in an id_token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:58):
isaacvetter commented on Issue #91:
## :telephone_receiver: II Working Group Vote (5-30-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
xx moved the following disposition, seconded by xx
Disposition: Question Answered
Disposition Comment: Will update the specification to clarify that, if using SMART, the AS shall respect the SMART OIDC scopes --openidandfhirUser.Discussion:
Since we don't require SMART, we can't absolutely require OIDC.
When a FHIRcast integration is using our recommended SMART on FHIR as authnz, is OIDC required? Here's the relevant details in SMART:
- http://www.hl7.org/fhir/smart-app-launch/conformance/index.html#single-sign-on
- http://www.hl7.org/fhir/smart-app-launch/#step-1-app-asks-for-authorization
:+1: For: 11
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada
Github Notifications (FHIRcast) (Jun 18 2019 at 15:58):
wmaethner labeled Issue #91:
## May 2019 Ballot Comment: Is OIDC support required?
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-Q ClarificationSummary: Is OIDC support required?
Comment: Does FHIRcast require the SMART server to support OIDC? Currently, there's no explicit requirement and SMART itself doesn't exactly require it.
Existing wording: Per SMART, when scopes of openid and fhirUser are granted, the app will additionally receive the current user's identity in an id_token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:52):
wmaethner closed Issue #91:
May 2019 Ballot Comment: Is OIDC support required?
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Session Discovery
Url:
Type: A-Q ClarificationSummary: Is OIDC support required?
Comment: Does FHIRcast require the SMART server to support OIDC? Currently, there's no explicit requirement and SMART itself doesn't exactly require it.
Existing wording: Per SMART, when scopes of openid and fhirUser are granted, the app will additionally receive the current user's identity in an id_token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Last updated: Apr 12 2022 at 19:14 UTC
