Discussion: RP Yadis URL?

Recordon, David drecordon at verisign.com
Sun Oct 15 19:10:36 UTC 2006


Well it seems like this would make sense for the RP to send during the
"associate" request versus with every "checkid_*" request.

I'm torn if this parameter should be added to the spec at this time or
not.  Adding the parameter is conceptually simple, though I don't think
there is agreement on what the RP should be publishing in their Yadis
file.  There is the section
http://openid.net/specs/openid-authentication-2_0-10.html#anchor42 which
has the RP publish a return_to URL, though the section was meant to be
removed as that URL may not be the right entry point to start a
transaction.

So I'm 0 for adding it, but against either:
A) Delaying the spec to figure out what the RP should publish
B) Acting rashly to figure out what the RP should publish

So I'd propose the "openid.yadis_location" parameter be added with the
description of "URL of the Relying Party's Yadis discovery document
describing services the Relying Party provides.  At this time, the exact
list of services has not been defined, though due to the nature of the
protocol they can be defined seperatly."

Though writing that just makes all the interoperability warnings go off
in my head.

I'd rather see us do this right or not do it at all right now.

--David 

-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of Drummond Reed
Sent: Sunday, October 15, 2006 9:59 AM
To: 'Johannes Ernst'; specs at openid.net
Subject: RE: Discussion: RP Yadis URL?

+1. All of the "defined algorithms for obtaining the XRDS document" from
either a URL or XRI will be going into Working Draft 11 of XRI
Resolution 2.0 starting this week. So it seems all the OpenID
Authentication 2.0 spec needs to specify is that they work against the
return_to URL.

=Drummond 

-----Original Message-----
From: specs-bounces at openid.net [mailto:specs-bounces at openid.net] On
Behalf Of Johannes Ernst
Sent: Sunday, October 15, 2006 12:00 AM
To: specs at openid.net
Subject: Re: Discussion: RP Yadis URL?

Yes. Or any of the other defined algorithms for obtaining the XRDS file,
given the return_to URL.

On Oct 14, 2006, at 23:50, Dick Hardt wrote:

> I assume you are referring to the return_to URL?
>
> Current libraries add all kinds of parameters to that URL, would you 
> be suggesting that the IdP does a GET on the return_to URL with 
> content-type of XRDS?
>
> If so, then we should add that to the spec. I'd then like to get clear

> on what would need to be in the Yadis file for indicating the 
> login_url.
>
> -- Dick
>
> On 14-Oct-06, at 11:43 PM, Johannes Ernst wrote:
>
>> Given that the RP has at least one URL, we can perform regular Yadis 
>> discovery on it. (Likely, all of the RP's URLs point to the same 
>> Yadis document.)
>>
>> I don't think an extension to the protocol is needed.
>>
>> On Oct 14, 2006, at 22:39, Dick Hardt wrote:
>>
>>> Currently there is no method for the IdP to learn anything about the

>>> RP.  As a path for extensibility, would anyone have a problem with 
>>> having an optional parameter in the AuthN Request for the location 
>>> of the RP's Yadis document?
>>>
>>> -- Dick
>>> _______________________________________________
>>> specs mailing list
>>> specs at openid.net
>>> http://openid.net/mailman/listinfo/specs
>>
>> Johannes Ernst
>> NetMesh Inc.
>>
>> <lid.gif>
>>  http://netmesh.info/jernst
>>
>>
>>
>>
>> _______________________________________________
>> specs mailing list
>> specs at openid.net
>> http://openid.net/mailman/listinfo/specs

Johannes Ernst
NetMesh Inc.


_______________________________________________
specs mailing list
specs at openid.net
http://openid.net/mailman/listinfo/specs




More information about the specs mailing list