From W3C Wiki
There are two different ways of combining these technologies:
- foaf+ssl enabled OpenId provider, which allows people with foaf+ssl certificates to use all OpenId enabled services on the web.
- foaf+ssl+openid which is very close to the foaf+ssl user experience: ie: no need for the user to remember his WebId or his password. The aim of this is to make it easy for web sites that want to use FOAF+SSL to do so by using an external service. This is very useful for web servers that do not have an https stack.
- An insecure delegated login system, shows how one can do foaf+ssl identification insecurely (but sometimes security is not needed). 2 lines of php code. Adding a few OpenId tricks to this gives us the more secure foaf+ssl+openid.
- openid4.me a web service that will give an openid to anyone with a WebId, using identification based on foaf+ssl.
- A foaf+ssl enabled OpenId provider in 100 lines of Perl code
- Using FOAF+SSL+OpenID with OpenLink Data Spaces