<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Connect dosen't mention the token revocation extension at all.<div><br></div><div>There needs to be a registry for this sort of extension. We had hoped that that would be part of the IETF dynamic registration spec, but that has stalled in the WG thanks to parties unnamed.</div><div><br></div><div>I don't think adding it to the openID dynamic reg spec would be worth triggering another review cycle.</div><div><br></div><div>We could possibly do a short standalone document on Configuring Token revocation for Connect here we could document the Discovery and registration parameters.</div><div>We probably should have added it as a optional parameter after revocation became a RFC but that is water under the bridge.</div><div><br></div><div>I think it should be documented separately as a RFC or Connect document.</div><div><br></div><div>John B.</div><div><br><div><div>On Jan 24, 2014, at 6:57 PM, Tim Bray <<a href="mailto:tbray@textuality.com">tbray@textuality.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Feels like a bug.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 24, 2014 at 1:41 PM, Brian Campbell <span dir="ltr"><<a href="mailto:bcampbell@pingidentity.com" target="_blank">bcampbell@pingidentity.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">A colleague asked me yesterday if the token revocation endpoint (from RFC7009 [1]) was one of the OpenID Provider Metadata parameters[2]. Which it is not. But should we consider adding it? <br>
<br>[1] <a href="http://tools.ietf.org/html/rfc7009" target="_blank">http://tools.ietf.org/html/rfc7009</a><br>
[2] <a href="http://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata" target="_blank">http://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata</a><br></div>
<br>_______________________________________________<br>
Openid-specs-ab mailing list<br>
<a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-ab</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.net</a><br>http://lists.openid.net/mailman/listinfo/openid-specs-ab<br></blockquote></div><br></div></body></html>