[OpenID] suggested server for private SSO using openid?

[SitG Admin]

>* A library is not what I'm after.  I'm looking for a installable 
>solution I don't have to spend time developing a system around.

So, you don't even have an interaction framework for these sites yet? 
You're essentially looking at building them from the authentication 
(as foundation) up, not taking an existing system and trying to 
integrate OpenID into it?

There are common content-publishing solutions such as WordPress, some 
of which (*cough* WP) don't support OpenID natively, but can be made 
to do so with plugins. I'm currently developing a system that can 
automatically scale as further users arrive (to upgrade the system 
that requires my manual intervention, but for private content 
customized to existing clients that hasn't been a problem), but it'll 
be at least a few days before this is ready (and probably much closer 
to a few weeks). When it's done I'll open-source the code, of course 
:)

>From openid.net:
>*  phpMyID - a standalone, single user identity provider.
>(As it says, single user)

It can be modified to support multiple users. In addition to the 
method described on phpMyID's forums, I worked out a quick hack that 
achieves the same purpose (but, again, requiring manual intervention 
for each new user - I only did it for testing, so, again, wasn't a 
problem).

>* Clamshell - standalone, multi-user OpenID server.
>(looks like a nice system but doesn't list jblow.example.com as an ID format.

Since you're using PHP, you can include the starting Clamshell file 
from a script that looks at your $_SERVER['HTTP_HOST'] string and 
extracts the 'jblow' part from it.

(If you get any "not found" errors, try fixing the active directory 
to wherever Clamshell is located - sorry, don't know the command for 
this, I fixed it by adjusting relative include paths to absolute for 
the openidenabled.com library.)

>Still it has several options which suggests it's flexible.  But 
>data isn't stored in a database)

Are you after "database" in general or MySQL in particular?

I was thinking about memcached back when I read your first message 
but then I noticed that you said the server would *not* be under 
heavy load (big difference there) ;)

-Shade