[OpenID] [foaf-protocols] Lack of browser support

[Story Henry]

On 26 Feb 2010, at 14:33, Nathan wrote:

> Hi All,
> 
> I'm wanting to roll out FOAF+SSL to a clients site, however certain
> browsers don't pass the security certificates (like blackberry's) any
> standard way around this (assuming just a normal login?) + how to sync
> this up to access-control when all user data is stored in public graph /
> users foaf?

Yes, this is a very good question. And indeed this is where OpenId comes in useful.
  
If you can make the user's home page point both to his foaf and to an OpenId provider, then a knowledgeable service can get information from his foaf too. This was an initial suggestion I made a while ago

   http://blogs.sun.com/bblfish/entry/foaf_openid

[Is this still the right way to link to a foaf?]

If it is not a problem that the information be public then this is very nice. 

 A service like http://openid4.me/ could help out here, by allowing people with such devices to create a local login, so that someone can login on openid4.me with foaf+ssl, and having proved that he is that user, could then get a username/password for when using a device that does not use certificates correctly.

  The advantage of this is that the user's profile is stored on his homepage, and that openid4.me is just a protocol conversion proxy.




> 
> Regards,
> 
> Nathan