<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">The structured value should be showing up in introspection, I believe. If it’s not, that’s probably a bug. <div class=""><br class=""></div><div class="">But to be honest, nobody uses structured scopes in deployment that I’m aware of. The feature was slated to be deprecated in 1.2 and removed in 1.3. <div class=""><br class=""></div><div class=""> — Justin</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jun 30, 2015, at 4:45 PM, Luiz Omori <<a href="mailto:luiz.omori@duke.edu" class="">luiz.omori@duke.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; font-size: 14px; font-family: Calibri, sans-serif;" class="">
<div class="">Hi,</div>
<div class=""><br class="">
</div>
<div class="">I’ve created a structured scope "patient/*.write" and a client application that has it. Then created one request including "patient/*.write” and another including "patient/*.write:rate.50”. The login UI reflected both just fine and I did get access_tokens
for both requests however the latter failed to show up in the response from the token Introspection. Is this normal behaviour? If yes, what is the rationale behind it?</div>
<div class=""><br class="">
</div>
<div class="">Regards,</div>
<div class="">Luiz</div>
</div>
_______________________________________________<br class="">mitreid-connect mailing list<br class=""><a href="mailto:mitreid-connect@mit.edu" class="">mitreid-connect@mit.edu</a><br class="">http://mailman.mit.edu/mailman/listinfo/mitreid-connect<br class=""></div></blockquote></div><br class=""></div></div></body></html>