<!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">
Also, HTTPS is easier and cheaper with <a class="moz-txt-link-freetext" href="https://op.com/username">https://op.com/username</a> than
<a class="moz-txt-link-freetext" href="https://username.op.com">https://username.op.com</a>. The former case needs one SSL server cert to
cover the entire user population; the latter requires a wildcard cert
(iirc, more expensive than a single server cert) or a cert per username.<br>
<br>
Cheers,<br>
<br>
Pat<br>
<br>
Mark Wahl wrote:
<blockquote cite="mid:46AFF879.60204@informed-control.com" type="cite">
<pre wrap="">Jamie McClelland wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Any suggestions would be welcome (including a link to RTFM :).
</pre>
</blockquote>
<pre wrap=""><!---->Coincidentally I mentioned some of the differences in constraints
in equality matching and encoding of OpenID URIs containing a userid
in the host versus those containing a userid in the path, in a recent
blog post "Issues with internationalizing domain names",
<a class="moz-txt-link-freetext" href="http://www.ldap.com/1/commentary/wahl/20070729_01.shtml">http://www.ldap.com/1/commentary/wahl/20070729_01.shtml</a>
Mark Wahl
Informed Control Inc.
_______________________________________________
general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:general@openid.net">general@openid.net</a>
<a class="moz-txt-link-freetext" href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
Pat Patterson - <a class="moz-txt-link-abbreviated" href="mailto:pat.patterson@sun.com">pat.patterson@sun.com</a>
Federation Architect,
Sun Microsystems, Inc.
<a class="moz-txt-link-freetext" href="http://blogs.sun.com/superpat">http://blogs.sun.com/superpat</a>
</pre>
</body>
</html>