CiviCRM Community Forums (archive)

I was in the same predicament and found something called phpMyID fit my needs perfectly.  It is basically a config file based, standalone identity provider, it consists of two php scripts and can be deployed in a few minutes.

I created a directory in my web site document root, openid, and copied MyID.php to it.  I then created directories underneath the openid directory for each user, and copied MyID.config.php to them, renamed as index.php.

/openid
    MyID.php
    index.php (empty file to prevent directory listings of the /openid directory)
    /userA
        index.php (MyID.php)
    /userB
        index.php (MyID.php)
    /userC
        index.php (MyID.php)


Decide on a realm, it can be anything, say "MyRealm".  For each user get the md5 string for their password.  In my case mysql was available so I used it.

select md5('userA:MyRealm:PasswordForUserA');
select md5('userB:MyRealm:PasswordForUserB');
and so on...

Edit each user's index.php:

• change auth_username to the username
• change auth_password to the md5 encoded password generated above
• uncomment auth_realm and set it to your realm (i.e. MyRealm)
• near the bottom of the file, change require('MyID.php'); to require('../MyID.php');

The configured users can now use identity urls like: http://server.domain.com/openid/userA/, http://server.domain.com/openid/userB/, etc...

Of course, you need to set file permissions appropriately if you are on a shared server, to prevent other users from being able to view those credentials in the index.php's.