<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; ">We could have made the issuer a full path to the discovery document. The decision was to make the issuer shorter by placing the discovery document at a well known location relative to the issuer URI. The .well-known directory is a place where system configuration files are likely to live. Some large IdP may be using smart TLS terminators to direct this to a compleatly separate server from regular content. Putting the config there seemed to make administrative sense.<div><br></div><div>Later in the process supporting multi-tennent per domain name was identified as important. That was when paths were allowed in the issuer as there were originally not part of the issuer. </div><div>Adding the same relative path to the URI containing a path made the client processing easier and did not change the simple case</div><div><br></div><div>John</div><div><br><div><div>On 2013-07-29, at 3:09 PM, Torsten Lodderstedt <<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<div><p>I don't get that argument. From my perspective, using .well-known makes sense if one does not use any other discovery mechanism. Then ./well-known allows to place meta data at a certain location (root folder) on a host. That's simple.</p><p>OIDC works completely different as it allows to place this data anywhere (with respect to the URL) and discovers this location. </p><p>Am 29.07.2013 14:55, schrieb Nat Sakimura:</p>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2px solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div dir="ltr">General answer, I guess, is that we wanted to minimize the URI pollution - that we should confine the URI pollution just withing .well-known folders. </div>
<div class="gmail_extra"><br><br>
<div class="gmail_quote">2013/7/29 Torsten Lodderstedt <span><<a href="mailto:torsten@lodderstedt.net">torsten@lodderstedt.net</a>></span><br>
<blockquote class="gmail_quote" style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;">Hi all,<br><br> I just took a look on the OIDC discovery spec. Why does it use .well-known? I'm asking since it deviates from the RFC in that it allows for path components (in order to support multi-tenancy) and the URL itself is either discovered via WebFinger or obtained out of band. Why not just obtain the connect config base URL that way and directly request the metadata. What is the value of adding "/.well-known" to the URL?<br><br> regards,<br> Torsten.<br> ______________________________<span style="text-decoration: underline;"></span>_________________<br> Openid-specs-ab mailing list<br><a href="mailto:Openid-specs-ab@lists.openid.net">Openid-specs-ab@lists.openid.<span style="text-decoration: underline;"></span>net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs-ab">http://lists.openid.net/<span style="text-decoration: underline;"></span>mailman/listinfo/openid-specs-<span style="text-decoration: underline;"></span>ab</a></blockquote>
</div>
<br><br clear="all">
<div> </div>
-- <br>Nat Sakimura (=nat)
<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/">http://nat.sakimura.org/</a><br>@_nat_en</div>
</div>
</blockquote>
<div> </div>
</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>