<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Perhaps just not calling it out as opaque. We don't say that about the user-info access token, because it is assumed in OAuth.<div><br></div><div>I am leaning towards describing it as the access token for the Check Session endpoint.</div><div><br></div><div>I asked in another email if id_token is perhaps a bad name? Perhaps session?</div><div><br></div><div>John B.<br><div><div>On 2011-08-16, at 7:32 PM, Johnny Bufu wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">To me it means that a lite client doesn't have to understand its contents, parse or extract data from it. Just store, compare or pass it along as required by the protocol.<br><br>I still think that the term "opaque" should be targeted at one or more parties that handle the token, not at a document.<br><br>Johnny</span></span></blockquote></div><br></div></body></html>