Has anyone done a comparison between this spec and OAuth? It really
seems like an unnecessary duplication of work given the 8 months we've
put into it so far...
Chris
Sent from my iPhone
On Sep 3, 2007, at 2:22 PM, Martin Atkins <[EMAIL PROTECTED]>
wrote:
> John Ehn wrote:
>> Martin,
>>
>
John Ehn wrote:
> Martin,
>
> Thanks for the response! I'm looking at those specs now, and I really
> like the flow of the HTTP Authentication spec, because it looks like
> it's solving the problem of passing the OpenID Identifier to the RP in
> an automated way, which is really cool. Looks li
Martin,
Thanks for the response! I'm looking at those specs now, and I really like
the flow of the HTTP Authentication spec, because it looks like it's solving
the problem of passing the OpenID Identifier to the RP in an automated way,
which is really cool. Looks like it needs to be "fleshed out
John Ehn wrote:
> The Inline Authentication Extension attempts to solve the problem of
> legacy and interactive applications (Telnet/SSH) that are unable to
> launch a client Web Browser to perform an authentication request.
>
> http://extremeswank.com/openid_inline_auth.html
>
> This is done thr
Hans,
Yes, the Client App is expected to implement all the important parts of an
OpenID 2.0 Relying Party. This means it will support XRI, Yadis, and HTML
discovery.
It's unlikely systems will have clashing namespaces, but is possible (most
corporate user accounts don't begin with "=", "@", "+",
Interesting. I like that it's short and technically well written.
So in practice a Client App would need to be able to distinguish the classes
of OpenID identifiers, so it know when to do the OpenID authn call, right?
Does that mean some existing systems may have clashing namespaces (for
instance,
The Inline Authentication Extension attempts to solve the problem of legacy
and interactive applications (Telnet/SSH) that are unable to launch a client
Web Browser to perform an authentication request.
http://extremeswank.com/openid_inline_auth.html
This is done through the use of "verification
