[OpenID] Using OpenID outside of the browser

[Brendan Taylor]

I've written a web-based Atom Publishing Protocol client[1] that uses
OpenID for identifying users. It seems to me that since I have a user's
OpenID anyways, it makes sense to include it when publishing an entry;
the problem is that while the client knows the user controls that URL,
there is no way (that I know of) for the client to prove that to another
server.

A more general case: I would like to let people comment on my blog using
the Atom Publishing Protocol. I would also like to use and verify their
OpenIDs for identification. But most APP clients aren't going to be part
of a browser, and so the login-redirect-set cookie dance seems out of
place.

What's the best way to marry OpenID and non-browser clients?

1: <http://necronomicorp.com/pushpin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070429/af0dbe7e/attachment-0002.pgp>