<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Helvetica, Arial, sans-serif">Very interesting. Are these
long term certificates? Will prooveme.com manage the generation of new
certificates and delivery to flickr when the old one is about to
expire? or will that be the user's responsibility?<br>
<br>
Thanks,<br>
George<br>
</font><br>
Nic James Ferrier wrote:
<blockquote cite="mid878xeis7zj.fsf@tapsellferrier.co.uk" type="cite">
<pre wrap="">Pat Cappelaere <a class="moz-txt-link-rfc2396E" href="mailto:pat@cappelaere.com"><pat@cappelaere.com></a> writes:
</pre>
<blockquote type="cite">
<pre wrap="">Is there a proposed standard or best-practice to pass along openid
information to web services that can be accessed across other domains?'
Example:
User logs on to main site.
User performs some action (distributed search for example)
Main site accesses web services across many remote sites on behalf of user.
Might be nice to have something like:
<a class="moz-txt-link-freetext" href="http://www.example.com/service?openid=xxx">http://www.example.com/service?openid=xxx</a>
Remote site should be able to validate user and even access user profile
information (if user agrees, of course)
</pre>
</blockquote>
<pre wrap=""><!---->
One of the things we're hoping to do with prooveme.com is to make
it possible to create client certificates to delegate to other sites
so they can authenticate, with your permission and in the way you
want, to 3rd parties.
So if you want flikr to post particular tagged photos to your blog you
can create a certificate which allows authenticating to one site only
and then give it to flikr.
Flikr then uses your OpenID and your prooveme.com certificate to
authenticate on your behalf and post photos.
</pre>
</blockquote>
</body>
</html>