<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Structured scopes aren't used in OIDC, but are a feature that was
added to support the BlueButton+ REST specification:<br>
<br>
<a class="moz-txt-link-freetext" href="http://bluebuttontoolkit.healthit.gov/blue-button-plus-pull/#scopes">http://bluebuttontoolkit.healthit.gov/blue-button-plus-pull/#scopes</a><br>
<br>
The idea was that you could provide an additional parameter, like a
record identifier, in addition to the core scope. In theory this
would allow clients to specify more exactly what they wanted access
to. In practice, it never caught on and it's a bit of a vestigial
feature in MITREid Connect that we're probably going to remove in a
future release (or at least turn into an add-on).<br>
<br>
For your use case, having two separate scopes makes more sense. Your
resources can decide if the "write" scope also allows "read" without
doing anything special.<br>
<br>
-- Justin<br>
<br>
<div class="moz-cite-prefix">On 8/26/2015 9:30 PM, Tony Fendall
[DATACOM] wrote:<br>
</div>
<blockquote
cite="mid:4a1675d04f6c4b4e9986597435acf68a@DNZAKEX4.datacom.net.nz"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi all<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Can anyone point me towards documentation
of structured scopes and how they work? I couldn’t find any
references to structured scopes in the OIDC docs.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">In my app I want to provide two scopes.
One allows read-only access to some data, the other should
provide write access. I could create these as independent
scopes, but I had a hunch that structured scopes might work
here as hierarchical scopes (and automatically give anyone
with write access read access also). Am I on the right track,
or do structured scopes mean something different?<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="mso-fareast-language:EN-NZ">Thanks<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:6.0pt"><b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:#003366;mso-fareast-language:EN-NZ"
lang="EN-US">Tony Fendall</span></b><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-NZ"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-top:6.0pt"><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-NZ"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-top:6.0pt"><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:EN-NZ"
lang="EN-US">Solution Architect<br>
Datacom New Zealand | 210 Federal Street, Auckland 1010,
New Zealand<br>
Email: </span><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:blue;mso-fareast-language:EN-NZ"
lang="EN-US"><a moz-do-not-send="true"
href="mailto:tonyf@datacom.co.nz"><span
style="color:#0563C1">tonyf@datacom.co.nz</span></a></span><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:EN-NZ"
lang="EN-US">
</span><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#7F7F7F;mso-fareast-language:EN-NZ"
lang="EN-US">|
</span><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:gray;mso-fareast-language:EN-NZ"
lang="EN-US">Ph: +64-9-303-1489
</span><span
style="font-size:8.0pt;font-family:"Arial",sans-serif;color:#7F7F7F;mso-fareast-language:EN-NZ"
lang="EN-US">| Mob: +64-21-130-8992</span><span
style="font-size:10.0pt;font-family:"Arial",sans-serif;color:black;mso-fareast-language:EN-NZ"><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
mitreid-connect mailing list
<a class="moz-txt-link-abbreviated" href="mailto:mitreid-connect@mit.edu">mitreid-connect@mit.edu</a>
<a class="moz-txt-link-freetext" href="http://mailman.mit.edu/mailman/listinfo/mitreid-connect">http://mailman.mit.edu/mailman/listinfo/mitreid-connect</a>
</pre>
</blockquote>
<br>
</body>
</html>