[OpenID] identity url suggested formats?

[Steven Livingstone]

A cert per username sounds like a good option to have - especially as the concept moves forward. A wildcard to cover everyone else but those who have their own certificates - businesses and high end users may have good reasons for this.
Most providers won't worry too much about the cost of a wildcard cert i would have thought.
 
I have used user.domain.org , but one issue is making sure certain characters are not used in the username (such as periods and spaces) which can screw up the logic.
 
steven
http://livz.org


Date: Tue, 31 Jul 2007 20:33:46 -0700From: Andrew.Patterson at Sun.COMTo: Mark.Wahl at informed-control.comCC: general at openid.netSubject: Re: [OpenID] identity url suggested formats?
Also, HTTPS is easier and cheaper with https://op.com/username than https://username.op.com. 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.Cheers,PatMark Wahl wrote: 
Jamie McClelland wrote:
  
Any suggestions would be welcome (including a link to RTFM :).
    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",
http://www.ldap.com/1/commentary/wahl/20070729_01.shtml


Mark Wahl
Informed Control Inc.

_______________________________________________
general mailing list
general at openid.net
http://openid.net/mailman/listinfo/general
  -- 
Pat Patterson - pat.patterson at sun.com
Federation Architect,
Sun Microsystems, Inc.
http://blogs.sun.com/superpat

_________________________________________________________________
Don't get caught with egg on your face. Play Chicktionary!  
http://club.live.com/chicktionary.aspx?icid=chick_wlmailtextlink
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-general/attachments/20070801/04799df3/attachment-0002.htm>