<html><head></head><body><div style="color:#000; background-color:#fff; font-family:verdana, helvetica, sans-serif;font-size:16px"><div id="yui_3_16_0_1_1444841252567_17677"><span id="yui_3_16_0_1_1444841252567_17702">Hi Justin,<br></span></div><div id="yui_3_16_0_1_1444841252567_17704"><span id="yui_3_16_0_1_1444841252567_17702"><br></span></div><div id="yui_3_16_0_1_1444841252567_17734"><span id="yui_3_16_0_1_1444841252567_17702">That's a real nice sequence of actions list.</span></div><div id="yui_3_16_0_1_1444841252567_18003"><br><span id="yui_3_16_0_1_1444841252567_17702"></span></div><div id="yui_3_16_0_1_1444841252567_18002"><span id="yui_3_16_0_1_1444841252567_17702">I would like to add few more points to it.</span></div><div id="yui_3_16_0_1_1444841252567_18001"><br><span id="yui_3_16_0_1_1444841252567_17702"></span></div><div id="yui_3_16_0_1_1444841252567_18000"><span id="yui_3_16_0_1_1444841252567_17702">5. Validate if JWT token expiration to see if the token is still valid.</span></div><div class="" dir="ltr" id="yui_3_16_0_1_1444841252567_17911"><span class="" id="yui_3_16_0_1_1444841252567_17702">6. Validate mandatory claims to be fulfilled. [ I come from OASIS SAML and XACML background for healthcare. In that we have used a OASIS XACML <b class="" id="yui_3_16_0_1_1444841252567_18032">XSPA(</b></span><font id="yui_3_16_0_1_1444841252567_18184" size="2">Cross-Enterprise Security and Privacy Authorization)</font></div><div dir="ltr" id="yui_3_16_0_1_1444841252567_17911"><span id="yui_3_16_0_1_1444841252567_17702"> profile to enforce mandatory and optional set of claims for a policy]</span></div><div id="yui_3_16_0_1_1444841252567_18270" dir="ltr"><br><span id="yui_3_16_0_1_1444841252567_17702"></span></div><div id="yui_3_16_0_1_1444841252567_18299" dir="ltr"><span id="yui_3_16_0_1_1444841252567_17702">Cheers</span></div><div id="yui_3_16_0_1_1444841252567_18300" dir="ltr"><span id="yui_3_16_0_1_1444841252567_17702">Vivek Biswas, CISSP<br></span></div><div id="yui_3_16_0_1_1444841252567_18330" dir="ltr"><span id="yui_3_16_0_1_1444841252567_17702">www.linkedin.com/in/vivekbiswas<br></span></div><div id="yui_3_16_0_1_1444841252567_17910"><span id="yui_3_16_0_1_1444841252567_17702"></span></div><br> <div id="yui_3_16_0_1_1444841252567_17699" style="font-family: verdana, helvetica, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1444841252567_17698" style="font-family: HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif; font-size: 16px;"> <div id="yui_3_16_0_1_1444841252567_17701" dir="ltr"> <hr id="yui_3_16_0_1_1444841252567_17700" size="1"> <font id="yui_3_16_0_1_1444841252567_17735" face="Arial" size="2"> <b><span style="font-weight:bold;">From:</span></b> Justin Richer <jricher@MIT.EDU><br> <b><span style="font-weight: bold;">To:</span></b> openid-specs-heart@lists.openid.net <br> <b id="yui_3_16_0_1_1444841252567_18334"><span id="yui_3_16_0_1_1444841252567_18333" style="font-weight: bold;">Sent:</span></b> Thursday, October 15, 2015 9:24 AM<br> <b id="yui_3_16_0_1_1444841252567_18332"><span id="yui_3_16_0_1_1444841252567_18331" style="font-weight: bold;">Subject:</span></b> [Openid-specs-heart] Fwd: Draft HEART Meeting Notes 2015-10-13<br> </font> </div> <div id="yui_3_16_0_1_1444841252567_17697" class="y_msg_container"><br><div id="yiv2603482855"><div id="yui_3_16_0_1_1444841252567_17696">Forwarding the off-list conversation that somehow got the “-bounces” address CC’d instead of the real list.<div id="yui_3_16_0_1_1444841252567_17867" class="yiv2603482855"><br class="yiv2603482855"></div><div id="yui_3_16_0_1_1444841252567_17695" class="yiv2603482855"> — Justin<br class="yiv2603482855"><div id="yui_3_16_0_1_1444841252567_17694"><br class="yiv2603482855"><blockquote id="yui_3_16_0_1_1444841252567_17693" type="cite" class="yiv2603482855"><div id="yui_3_16_0_1_1444841252567_17737" class="yiv2603482855">Begin forwarded message:</div><br class="yiv2603482855Apple-interchange-newline"><div id="yui_3_16_0_1_1444841252567_17739" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;" class="yiv2603482855"><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855"><b class="yiv2603482855">From: </b></span><span id="yui_3_16_0_1_1444841252567_17738" style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855">Dale Moberg <<a rel="nofollow" ymailto="mailto:dale.moberg@orionhealth.com" target="_blank" href="mailto:dale.moberg@orionhealth.com" class="yiv2603482855">dale.moberg@orionhealth.com</a>><br class="yiv2603482855"></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;" class="yiv2603482855"><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855"><b class="yiv2603482855">Subject: </b></span><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855"><b class="yiv2603482855">Re: [Openid-specs-heart] Draft HEART Meeting Notes 2015-10-13</b><br class="yiv2603482855"></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;" class="yiv2603482855"><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855"><b class="yiv2603482855">Date: </b></span><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855">October 15, 2015 at 12:22:53 PM EDT<br class="yiv2603482855"></span></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;" class="yiv2603482855"><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855"><b class="yiv2603482855">To: </b></span><span style="font-family:-webkit-system-font, Helvetica Neue, Helvetica, sans-serif;" class="yiv2603482855">Justin Richer <<a rel="nofollow" ymailto="mailto:jricher@mit.edu" target="_blank" href="mailto:jricher@mit.edu" class="yiv2603482855">jricher@mit.edu</a>>, Openid-specs-heart <<a rel="nofollow" ymailto="mailto:openid-specs-heart-bounces@lists.openid.net" target="_blank" href="mailto:openid-specs-heart-bounces@lists.openid.net" class="yiv2603482855">openid-specs-heart-bounces@lists.openid.net</a>><br class="yiv2603482855"></span></div><br class="yiv2603482855"><div id="yui_3_16_0_1_1444841252567_17748" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17747" style="word-wrap:break-word;font-size:14px;font-family:Calibri, sans-serif;" class="yiv2603482855">
<div class="yiv2603482855">:-) I thought you might have a favorable disposition toward an introspection service!</div>
<div id="yui_3_16_0_1_1444841252567_17746" class="yiv2603482855"><br class="yiv2603482855">
</div>
<span id="yiv2603482855OLK_SRC_BODY_SECTION" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17772" style="font-family:Calibri;font-size:11pt;text-align:left;border-width:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;border-top-color:rgb(181, 196, 223);" class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">From: </span>Justin Richer <<a id="yui_3_16_0_1_1444841252567_17778" rel="nofollow" ymailto="mailto:jricher@mit.edu" target="_blank" href="mailto:jricher@mit.edu" class="yiv2603482855">jricher@mit.edu</a>><br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">Date: </span>Thursday, October 15, 2015 at 9:21 AM<br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">To: </span>Dale Moberg <<a id="yui_3_16_0_1_1444841252567_17780" rel="nofollow" ymailto="mailto:dale.moberg@orionhealth.com" target="_blank" href="mailto:dale.moberg@orionhealth.com" class="yiv2603482855">dale.moberg@orionhealth.com</a>><br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">Cc: </span>Openid-specs-heart <<a rel="nofollow" ymailto="mailto:openid-specs-heart-bounces@lists.openid.net" target="_blank" href="mailto:openid-specs-heart-bounces@lists.openid.net" class="yiv2603482855">openid-specs-heart-bounces@lists.openid.net</a>><br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">Subject: </span>Re: [Openid-specs-heart] Draft HEART Meeting Notes 2015-10-13<br class="yiv2603482855">
</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div id="yui_3_16_0_1_1444841252567_17790" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17789" style="word-wrap:break-word;" class="yiv2603482855">
We’re not favoring JWT over introspection: in fact we’re mandating both simultaneously because the real world needs a balance between approaches. Coupled with the discovery system (also required), you can also use them together very nicely:
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855"> 1: RS gets a token, parses it as a JWT</div>
<div class="yiv2603482855"> 2: RS reads the issuer, discovers configuration</div>
<div class="yiv2603482855"> 3: RS pulls the public key of AS and checks signature</div>
<div id="yui_3_16_0_1_1444841252567_17788" class="yiv2603482855"> 4: RS introspects token at the AS (as just discovered)</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">By having both JWT and Introspection lets the RS figure out which model it wants to use, and it can always count on both being available.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Believe me, I’m actually a rather big fan of the service-based model: <a rel="nofollow" target="_blank" href="https://tools.ietf.org/html/draft-ietf-oauth-introspection" class="yiv2603482855">https://tools.ietf.org/html/draft-ietf-oauth-introspection</a> ;)</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855"> — Justin</div>
<div id="yui_3_16_0_1_1444841252567_17809" class="yiv2603482855"><br class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17808" class="yiv2603482855">
<blockquote id="yui_3_16_0_1_1444841252567_17807" type="cite" class="yiv2603482855">
<div class="yiv2603482855">On Oct 15, 2015, at 11:38 AM, Dale Moberg <<a rel="nofollow" ymailto="mailto:dale.moberg@orionhealth.com" target="_blank" href="mailto:dale.moberg@orionhealth.com" class="yiv2603482855">dale.moberg@orionhealth.com</a>> wrote:</div>
<br class="yiv2603482855Apple-interchange-newline">
<div id="yui_3_16_0_1_1444841252567_17806" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17805" style="word-wrap:break-word;font-size:14px;font-family:Calibri, sans-serif;" class="yiv2603482855">
<div class="yiv2603482855">Because I just located the drafts (thanks Justin!) I had missed a lot of what this group has as background context. I will soon find time to look at the drafts more carefully. Are there specific openid connect readings that we are profiling or
adapting in this group? (I am familiar with the core openid connect spec on the oauth2-protected, identity-information service for the (API) client. </div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div id="yui_3_16_0_1_1444841252567_17873" class="yiv2603482855">I am a bit concerned about using JWT instead of an unpredictable opaque token (with expiration) for access. I suspect this embellishment may be because of the deliberate omission (in core OAuth2) of the communication details between the resource
service/server and the authz & token issuing endpoint server. I have always thought that from a security architecture viewpoint that introspection style services would provide good ways to offload most security checking work at the API endpoints to a scalable
layer of introspection servers. Certainly cloud scalability models seem to favor a service approach, rather than an approach using structured token unpacking, with cryptographic operations and checks. </div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Perhaps you would be willing to explain to participants (or me) the case for using JWT in the way that is currently favored in our group? I can then provide my R&D group with the underlying thinking.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div id="yui_3_16_0_1_1444841252567_17804" class="yiv2603482855">I will also continue to think about how to bridge trust between multiple API user security domains with a central shared API server, in its own security domain. That may be an issue to be addressed elsewhere, however.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Thanks for your response!</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Dale Moberg</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<span id="yiv2603482855OLK_SRC_BODY_SECTION" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17882" style="font-family:Calibri;font-size:11pt;text-align:left;border-width:1pt medium medium;border-style:solid none none;padding:3pt 0in 0in;border-top-color:rgb(181, 196, 223);" class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">From: </span>Justin Richer <<a rel="nofollow" ymailto="mailto:jricher@mit.edu" target="_blank" href="mailto:jricher@mit.edu" class="yiv2603482855">jricher@mit.edu</a>><br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">Date: </span>Wednesday, October 14, 2015 at 5:24 PM<br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">To: </span>Dale Moberg <<a id="yui_3_16_0_1_1444841252567_17881" rel="nofollow" ymailto="mailto:dale.moberg@orionhealth.com" target="_blank" href="mailto:dale.moberg@orionhealth.com" class="yiv2603482855">dale.moberg@orionhealth.com</a>><br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">Cc: </span>Sarah Squire <<a rel="nofollow" ymailto="mailto:sarah@engageidentity.com" target="_blank" href="mailto:sarah@engageidentity.com" class="yiv2603482855">sarah@engageidentity.com</a>>, "<a rel="nofollow" ymailto="mailto:openid-specs-heart@lists.openid.net" target="_blank" href="mailto:openid-specs-heart@lists.openid.net" class="yiv2603482855">openid-specs-heart@lists.openid.net</a>" <<a rel="nofollow" ymailto="mailto:openid-specs-heart@lists.openid.net" target="_blank" href="mailto:openid-specs-heart@lists.openid.net" class="yiv2603482855">openid-specs-heart@lists.openid.net</a>><br class="yiv2603482855">
<span style="font-weight:bold;" class="yiv2603482855">Subject: </span>Re: [Openid-specs-heart] Draft HEART Meeting Notes 2015-10-13<br class="yiv2603482855">
</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div id="yui_3_16_0_1_1444841252567_17908" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17907" style="word-wrap:break-word;" class="yiv2603482855">
The JWT specified by the HEART OAuth spec is the result of the OAuth process, not the input into it. We’re specifying a JWT as the format of the access token in order to allow interoperability between RS and AS from different vendors and domains. We’re also
mandating support for token introspection for the same reason.
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div id="yui_3_16_0_1_1444841252567_17906" class="yiv2603482855">OpenID Connect further specifies JWT as the format for the ID token, which we’re inheriting directly.<br class="yiv2603482855">
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">We’re not using JWT assertions (RFC7521/7523) directly to get tokens, but we are using JWT assertions in client authentication, as defined in OpenID Connect Core as “private_key_jwt”. This is something we’re not inventing, but mandating (and
describing rationale for) its use. </div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">There is no fork or clash with other standards.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">We are not inventing any new grant types, but we are specifying that certain kinds of client applications need to use certain grant types.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Hope this helps,</div>
<div class="yiv2603482855"> — Justin</div>
<div id="yui_3_16_0_1_1444841252567_17905" class="yiv2603482855"><br class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17904" class="yiv2603482855">
<blockquote id="yui_3_16_0_1_1444841252567_17903" type="cite" class="yiv2603482855">
<div class="yiv2603482855">On Oct 14, 2015, at 2:53 PM, Dale Moberg <<a rel="nofollow" ymailto="mailto:dale.moberg@orionhealth.com" target="_blank" href="mailto:dale.moberg@orionhealth.com" class="yiv2603482855">dale.moberg@orionhealth.com</a>> wrote:</div>
<br class="yiv2603482855Apple-interchange-newline">
<div id="yui_3_16_0_1_1444841252567_17902" class="yiv2603482855">
<div id="yui_3_16_0_1_1444841252567_17901" style="word-wrap:break-word;font-size:14px;font-family:Calibri, sans-serif;" class="yiv2603482855">
<div style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855">Hi HEART people,</div>
<div style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855"><br class="yiv2603482855">
</div>
<div id="yui_3_16_0_1_1444841252567_17900" style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855">I am coming out of my mainly listen-mode participation to ask some questions. By way of introduction, I have been involved with the design and specification of inter-organizational security
solutions in the IETF (EDIINT- AS2 for logistics and supply chains), Rosettanet (choreographed XML exchanges for business processes for high-tech), OASIS/UNCEFACT ebXML(same as rosettanet, but for any organizations), W3C (wsdl, ws-policy, ws-splat for rpc/doc/SOA/whatever),
OMG and ISO(Unifi harmonization), UncefactMM/UBL(semantic compositionality models) GS1(EPCIS, IOT) and similar effots. But only recently addressing the healthcare domain with a focus of improving interoperability at both technical (security/protocol/API) and
semantic to promote use of clinical data in Machine Learning models of “actionable information” Enough with the buzz words.</div>
<div style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855"><br class="yiv2603482855">
</div>
<div style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855"><br class="yiv2603482855">
</div>
<div style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855"><font class="yiv2603482855" face="Calibri,sans-serif">"</font><span style="font-family:Arial;font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">We are not developing a standard.
We are developing </span><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">a profile of a standard.”</span></font></div>
<div class="yiv2603482855"><font style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">"</span></font><span style="font-family:Arial;font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">HEART
is primarily about user-mediated exchange, </span><span style="font-family:Arial;font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">but we can’t ignore clinical data exchange.</span><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">”</span></font></div>
<div style="font-family:Calibri, sans-serif;font-size:14px;" class="yiv2603482855"><span style="font-family:Arial;font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855"><br class="yiv2603482855">
</span></div>
<div class="yiv2603482855"><span style="font-family:Arial;font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">However, it does not seem we are profiling a standard (a relatively straightforward matter of subsetting a specific standard to trim out optionality,
and mandate the functionality organizational groups need, while remainling interoperable and open to multiple implementations), but instead saying how you want to use:</span></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">UMA + FHIR + OAuth2 + JWT + ??? —together within
</span></font><span style="font-size:15px;line-height:20px;white-space:pre-wrap;font-family:Arial;" class="yiv2603482855">the registration, delegation, data contribution, and related data sharing scenarios. In other words, you want to build a way to apply several
existing standards and have them work together interoperably (like an IETF applicability statement).</span></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855"><br class="yiv2603482855">
</span></font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855">My first question concerns the IETF OAuth group’s RFC 7521 that “…</span></font>provides a framework for the use of assertions with OAuth
2.0 in the form of a new client authentication mechanism and a new authorization grant type.”
<font class="yiv2603482855" face="Arial"><span style="font-size:16px;" class="yiv2603482855"> Is it agreed to include RFC 7521 within our profile? RFC 7523 "</span></font><span style="font-family:Courier;font-size:small;" class="yiv2603482855">JSON Web Token (JWT) Profile
</span><font class="yiv2603482855" face="Courier" size="2">for OAuth 2.0 Client Authentication and Authorization Grants”
</font><font class="yiv2603482855" face="Arial">already specifies a way to use JWT; in my opinion, it would clash with IETF work to fork an alternative approach to using JWT. If you plan to do this, I would be interested in your reasons for doing so.</font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><br class="yiv2603482855">
</font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial">The 7521/7523 profiling approach rapidly cuts down on our scope so that we do not have to worry how to specify using a signed JWT token to get an OAuth2 access token (via the newly defined grant type). If one of the
four previously defined OAuth 2 (RFC 6749) grant types are to be used, we would have to explain what the JWT is doing in the process. All the other grant types involve client ids, secrets, usernames and password credentials in various combinations. Would they
be combined with a JWT? How? Why? This seems to be a lot of effort, and personally I need a little motivation for undertaking trying to work through that amount of complexity.</font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><br class="yiv2603482855">
</font></div>
<div class="yiv2603482855">Now you could use those previous kinds of credentials and grant types in contacting a JWT issuing service (call it an “authentication authority”). Is that a step that needs explicit profiling in this group?</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">As far as Eve’s design patterns (organizational, role, individual entity), another way of slicing the designs up is by introducing an idea of “organizational or aggregated organizational security domain”</div>
<div class="yiv2603482855">I work for a company that creates “HIEs— health information exchanges” Some of these HIEs span lab organizations, pharmacies, urgent cares, clinics, optometrists, hospitals etc etc.” Some emerging ones span different types of organizations involved
in different aspects of healthcare — notably provider organizations and payer organizations. Each organization has its own security domain, but the HIE normally has a separate security domain. The main security problem is then defining the “trust bridge” allowing
these distinct security domains to share their data, subject to HIPAA and CFR 42 kinds of privacy constraints.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">To me, both the roles and individuals will be in an organizational context. The organizational context is typically identified by DNS domain names, and has a security domain within which credentials are submitted and checked. Typically the individuals
will have an identifier associated with the organization (e.g,, email address) and role(s). When an individual from security domain A wishes to use resources within security domain B, it gets an organizational token (JWT) issued by domain A and then submits
it to domain B, which can authorize access for the individual. This is a hard security problem to get resolved interoperably. Is this “pattern” one that we should profile? If it is I am all in. But if we are only interested in an individual’s capability to
set policy within a specific security domain, the security problem will lack interoperability in emerging data exchanges accessed via APIs (including FHIR dstuX when it emerges).</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Sorry for the detail but I have been as succinct as is consistent with explaining my questions.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">I will attach a diagram I have used to ask this question to Eve Maler (hi Eve!). Hoping to move us forward in getting clear about our profiling activity. I realize this is not a pure waterfall design pattern (use cases driving everying below),
but that is not agile, and we should all be able to be agile as needed.</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855">Dale Moberg</div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><br class="yiv2603482855">
</font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><br class="yiv2603482855">
</font></div>
<div class="yiv2603482855"><br class="yiv2603482855">
</div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855"><br class="yiv2603482855">
</span></font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855"><br class="yiv2603482855">
</span></font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855"><br class="yiv2603482855">
</span></font></div>
<div class="yiv2603482855"><font class="yiv2603482855" face="Arial"><span style="font-size:15px;line-height:20px;white-space:pre-wrap;" class="yiv2603482855"><br class="yiv2603482855">
</span></font></div>
</div>
<span class="yiv2603482855"><DT-FHIRCaseFiveBasics.docx></span>_______________________________________________<br class="yiv2603482855">
Openid-specs-heart mailing list<br class="yiv2603482855">
<a rel="nofollow" ymailto="mailto:Openid-specs-heart@lists.openid.net" target="_blank" href="mailto:Openid-specs-heart@lists.openid.net" class="yiv2603482855">Openid-specs-heart@lists.openid.net</a><br class="yiv2603482855">
<a rel="nofollow" target="_blank" href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" class="yiv2603482855">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><br class="yiv2603482855">
</div>
</blockquote>
</div>
<br class="yiv2603482855">
</div>
</div>
</div>
</div>
</span></div>
</div>
</blockquote>
</div>
<br class="yiv2603482855">
</div>
</div>
</div>
</span>
</div>
</div></blockquote></div><br class="yiv2603482855"></div></div></div><br>_______________________________________________<br>Openid-specs-heart mailing list<br><a ymailto="mailto:Openid-specs-heart@lists.openid.net" href="mailto:Openid-specs-heart@lists.openid.net">Openid-specs-heart@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-heart" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-heart</a><br><br><br></div> </div> </div> </div></body></html>