On Thu, May 24, 2007 at 10:19:08AM -0700, Josh Hoyt wrote:
On 5/24/07, Peter Watkins [EMAIL PROTECTED] wrote:
Shouldn't the spec clarify what is required for an HTML discovery to
uphold an assertion that triggers 11.2's discovery process?
The spec as it is currently written does not
On 25-May-07, at 11:18 AM, Peter Watkins wrote:
It's too bad Yadis doesn't allow embedding the XRDS document in
something like a META tag to avoid that second Yadis HTTP request
If you send an Accept header that includes application/xrds+xml
the OP can return the XRDS document on the first
Section 11.2 states
If the Claimed Identifier was not present in the request (openid.identity
was http://specs.openid.net/auth/2.0/identifier_select;), the Relying Party
MUST perform discovery on the Claimed Identifier in the response to make sure
that the OP is authorized to make assertions
On 24-May-07, at 8:19 AM, Peter Watkins wrote:
Section 11.2 states
If the Claimed Identifier was not present in the request
(openid.identity was http://specs.openid.net/auth/2.0/
identifier_select), the Relying Party MUST perform discovery on
the Claimed Identifier in the response to
On 5/24/07, Peter Watkins [EMAIL PROTECTED] wrote:
Shouldn't the spec clarify what is required for an HTML discovery to
uphold an assertion that triggers 11.2's discovery process?
The spec as it is currently written does not support using identifier
selection with HTML discovery. That was
