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@openid.net
http://openid.net/mailman/listinfo/specs
Johannes Ernst
NetMesh Inc.
<lid.gif>
http://netmesh.info/jernst
_______________________________________________
specs mailing list
specs@openid.net
http://openid.net/mailman/listinfo/specs
Johannes Ernst
NetMesh Inc.
http://netmesh.info/jernst
_______________________________________________
specs mailing list
specs@openid.net
http://openid.net/mailman/listinfo/specs
