[Openid-specs-ab] .well-known in OIDC Discovery

Nat Sakimura sakimura at gmail.com
Mon Jul 29 12:55:11 UTC 2013


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.


2013/7/29 Torsten Lodderstedt <torsten at lodderstedt.net>

> Hi all,
>
> 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?
>
> regards,
> Torsten.
> ______________________________**_________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.**net <Openid-specs-ab at lists.openid.net>
> http://lists.openid.net/**mailman/listinfo/openid-specs-**ab<http://lists.openid.net/mailman/listinfo/openid-specs-ab>
>



-- 
Nat Sakimura (=nat)
Chairman, OpenID Foundation
http://nat.sakimura.org/
@_nat_en
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20130729/2aeba7ff/attachment.html>


More information about the Openid-specs-ab mailing list