[Openid-specs-ab] token revocation endpoint in OP metadata
Michael.Jones at microsoft.com
Fri Jan 24 22:12:24 UTC 2014
I don't think this is a recall-class bug for the current specs. That being said, I think it should be added the next time they are revised or could be added as a separate spec. Does someone want to file an issue proposing this for a future revision or new spec so this isn't lost?
If we're being really diligent, we could also create a wiki page on the OpenID wiki with a title something like "Proposed OpenID Connect Additions", so people could refer to it before there's an actual spec, and reference it from the working group page. (No, I'm not volunteering to do this myself, at present. :))
From: openid-specs-ab-bounces at lists.openid.net [mailto:openid-specs-ab-bounces at lists.openid.net] On Behalf Of Brian Campbell
Sent: Friday, January 24, 2014 2:05 PM
To: Tim Bray
Cc: <openid-specs-ab at lists.openid.net>
Subject: Re: [Openid-specs-ab] token revocation endpoint in OP metadata
Okay, seems like there is some support for it and folks are already using "revocation_endpoint" for the parameter name, which makes sense.
On Fri, Jan 24, 2014 at 2:57 PM, Tim Bray <tbray at textuality.com<mailto:tbray at textuality.com>> wrote:
Feels like a bug.
On Fri, Jan 24, 2014 at 1:41 PM, Brian Campbell <bcampbell at pingidentity.com<mailto:bcampbell at pingidentity.com>> wrote:
A colleague asked me yesterday if the token revocation endpoint (from RFC7009 ) was one of the OpenID Provider Metadata parameters. Which it is not. But should we consider adding it?
Openid-specs-ab mailing list
Openid-specs-ab at lists.openid.net<mailto:Openid-specs-ab at lists.openid.net>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openid-specs-ab