[Openid-specs-ab] [openid/connect] discovery using issuer identifer w/ path component conflict with RFC 5785? (issue #638)

Brian Campbell issues-reply at bitbucket.org
Wed Aug 8 15:23:54 UTC 2012


--- you can reply above this line ---

New issue 638: discovery using issuer identifer w/ path component conflict with RFC 5785?
https://bitbucket.org/openid/connect/issue/638/discovery-using-issuer-identifer-w-path

Brian Campbell:

Appending the "/.well-known/openid-configuration" to an issuer identifier that has a path component per §3.1 of Discovery [1] seems like it might contradict RFC 5785 (or at least not really be in the spirit of RFC 5785). The first paragraph of §3 of the RFC [2] talks about the path component beginning with the "/.well-known/ and question #4 in the FAQ [3] talks about why per-directory well-known locations are not defined. 

Is this okay? It seems kind of iffy.


[1] http://openid.net/specs/openid-connect-discovery-1_0.html#anchor9 
[2] http://tools.ietf.org/html/rfc5785#section-3
[3] http://tools.ietf.org/html/rfc5785#appendix-B 


--

This is an issue notification from bitbucket.org. You are receiving
this either because you are the owner of the issue, or you are
following the issue.


More information about the Openid-specs-ab mailing list