<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Josh Hoyt wrote:
<blockquote
cite="mid:34714aad0709280838v4319e723r69909a8b9f6f9acb@mail.gmail.com"
type="cite">
<pre wrap="">
Not to pick on anybody, but the first site I tried failed to work with
HTTPS identifiers:
<a class="moz-txt-link-freetext" href="http://wikitravel.org/en/Special:OpenIDLogin">http://wikitravel.org/en/Special:OpenIDLogin</a>
I think, in general, it's going to be people with hosting accounts
where the programming environment was not linked to a SSL library, and
not independent properties. I'm willing to bet that there are also
sites (like Wikitravel) that didn't have any need for SSL support in
the past, so they made the (quite reasonable) choice when setting up
the machine not to install software that wasn't needed.
</pre>
</blockquote>
Josh, I think per concept, the RP doesn't have to implement SSL
(https). Obviously it would be preferred perhaps, but not a
requirement. Much different the ID provider should be the one with SSL
support and redirect to its own <a class="moz-txt-link-freetext" href="https://user.provider">https://user.provider</a><br>
<br>
<br>
<br>
<div class="moz-signature">-- <br>
<table border="0" cellpadding="0" cellspacing="0">
<tbody>
<tr>
<td colspan="2">Regards </td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
<tr>
<td>Signer: </td>
<td>Eddy Nigg, <a href="http://www.startcom.org">StartCom Ltd.</a></td>
</tr>
<tr>
<td>Jabber: </td>
<td><a href="xmpp:startcom@startcom.org">startcom@startcom.org</a></td>
</tr>
<tr>
<td>Blog: </td>
<td><a href="http://blog.startcom.org">Join the Revolution!</a></td>
</tr>
<tr>
<td>Phone: </td>
<td>+1.213.341.0390</td>
</tr>
<tr>
<td colspan="2"> </td>
</tr>
</tbody>
</table>
</div>
</body>
</html>