• Edit /etc/postgresql/8.3/main/pg_hba.conf

$ sudo /etc/init.d/postgresql-8.3 stop</ode>
<code>$ sudo vi /etc/postgresql/8.3/main/pg_hba.conf

Find this line:

#"local" is for Unix domain socket connections only
          local   all         all                              ident sameuser

Comment it out and add the following line:

           local   all         all                               md5

• Restart Postgresql

$ sudo /etc/init.d/postgresql-8.3 start

• Create the mailman user in the database

$ sudo su postgres
$ createuser mailman
 -> Shall the new role be a superuser? (y/n) n

 -> Shall the new role be allowed to create databases? (y/n) y

 -> Shall the new role be allowed to create more new roles? (y/n) n

• Assign a password to the DB mailman user

$ psql (this drops you into the sql interface for modifying the postgres db)
postgres=# alter user mailman password 'mailman';
ALTER ROLE

ctrl-D (to exit psql)
ctrl-D (to go back to original user shell)

Change to superuser:

 su 

Change to superuser postgres:

 su postgres 

Create database 'mailman_members'

 psql
 create database mailman_members owner mailman; 
 \c mailman_members

Create the table for storing mailman membership data

cd /usr/local/mailman
sudo bin/create_memtable

ssh into your abiwt account. Type the following commands

psql -d mailman_members -U mailman
password: <enter the password>
\d (to list the tables in the database)
select * from mailman_test;

We will be using three mailing lists : membership_test1 , membership_test2, membership_test3

Three users member1 , member2, member3 we will be using for testing the Common Authentication on dev.systers.org. The table below shows the user to the list mentioned above or whether in digest mode or not. (D) shows in digest mode.

You can navigate openidreg page through the following Use Cases.

User is directed to this page which is a client side script for the OpenID Consumer , i.e. when the user who has enabled her common authentication , and login using common authentication, so she will be directed to the OpenIDConsumer Page ,which works on http://dev.systers.org:8001. The Identifier will be http://dev.systers.org:8000/id/<username>/. This identifier will be used to verify for the DokuWiki . The Doku wiki that we will be using is on http://dev.systers.org/dokuwik/doku.php .

This page can be navigated through listinfo page for a particular mailing list.

The OpenID Provider for systers which uses the “mailman_membership” database and checks for authenticating the user. The OpenIDProvider is on http://dev.systers.org:8000/. It still need to be used through Web CGI which will be preferred as one can not run it by everytime logging in.

After the OpenID Consumer get verified for the Identifier from the Provider, a link on the Consumer shows a page which redirects her to the oiduserpage , which shows the list that user has subscribed and using the same list for the Common Authentication to all his lists.

User comes to this list when redirected from the oiduserpage . Client login page is similar to the Options page, but here user cannot Unsubscribe . And the password remider that will be sent to the user is the respective password for each list that she is being subscribed to.However it still ask for the password once that has been set for OpenID authentication of the user. After the password is being provided , user can access all her lists and change options from them without giving password repeatedly.

There is a small UI bug for the membership branch which shows when the admin tries to add a new Mailing List , although the changes are reflected in the mailman_members database as well as in the Mailing Lists's database , the new list is also shown on the listinfo page, it is basically a UI bug where we expect it to show the message for the list creation. Here is a bug report related to that Bug 619509