Issue 25: Dokumentation
Status:  Accepted
Owner: ----
Reported by themoose...@googlemail.com, Jan 25, 2011
I was searching for an explanation for openid.realm. I found a good one here: https://code.google.com/intl/de-DE/apis/accounts/docs/OpenID.html#Parameters
on this page are many parameters explained in a few words. Perhaps you could link to it as an external link or mention it in the wiki-system.

If I have more questions / suggestions related to the documentation, I will write them down in this issue.
Feb 14, 2011
Project Member #1 mewp...@gmail.com
Finally, wrote some documentation.
https://code.google.com/p/lightopenid/wiki/Configuration

Sorry for the unusually long delay.
Status: Done
Labels: -Type-Defect Type-Enhancement
Feb 19, 2011
#2 themoose...@googlemail.com
Hi mewp,

what do you think about providing a wiki-page with a possible database implementation?

Something like this:
Title: Extend an existing MySQL-login-system with OpenID

Requirements: You already have a login-system and you store some user-data in a MySQL Database which looks simmilar to this:

Usertable:
| id     | username  | password | prename  | lastname ...
| unique |

Then you can create a new table which stores the OpenIDs. Keep in mind that every user might have several openIDs, but no OpenID can belong to more than one user:

CREATE TABLE IF NOT EXISTS `UserOpenIDs` (
  `openid_url` varchar(255) NOT NULL,
  `user_id` int(11) NOT NULL,
  PRIMARY KEY (`openid_url`),
  KEY `user_id` (`user_id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;

You have to provide a possibility for users to "bind" their OpenIDs to their account and to sign in with their OpenIDs. You should also think about redesigning your registration process.
Feb 19, 2011
Project Member #3 mewp...@gmail.com
While it's not related to the library itself, it may be useful for some people.

However, writing such tutorial is not as simple as you might think. For example, the your approach to storing identities has a critical flaw -- URL-s can be much longer than 255 characters. While that may not happen often and may be a risk that you're willing to take for your own website, I can't tell people that it's The Right Way to do it.

Also, I'd have to write something about the registration process you've mentioned, and various other things (openid-only vs password auth + openid, for example).

So I probably will get to it eventually, but it'll take some time.
Status: Accepted
Mar 1, 2011
#4 themoose...@googlemail.com
Hi mewp,

do you know this project: https://code.google.com/p/openid-selector/ ?

I think lightopenid and the openid-selector might be a good combination for many projects. What do you think about setting a link to them? I'll propose that the openid-selector project, too.

cheers,
Martin
Mar 13, 2011
#5 themoose...@googlemail.com
Hi mewp,

on the homepage (https://code.google.com/p/lightopenid/) your wrote
"Works only as a consumer."

I think this is outdated. Now it works also as a privider, doesn't it?
Mar 14, 2011
Project Member #6 mewp...@gmail.com
I've added a link to openid-selector and updated the project summary.