[Systers-dev] Project Using Mailman Authentication

[Malveeka Tewari]

That sounds like a good pland and I am glad you want to follow up with my
code but if the use of REST API in  MM3 handles it in a better way - then
continuing the old approach is not the best idea ..

It'll be great if you can tell us why you want to take this approach instead
of using the Django framework

And then we can make a better decision about our approach I hope..

On Sat, Apr 3, 2010 at 9:37 AM, Jaideep Khandelwal <jdk2588 at gmail.com>wrote:

> After going through what Robin discussed and making a draft of what I think
> to carry forward the mailman authentication for single sign on for the
> Systers i have come with the plan :
>
> 1. As the last year Malveeka's project was to use a separate database table
> for OPEN ID'S to internal mailman  users and providing a seprate UI for the
> users registering at systers mailing list , so I would like to continue
> with
> Malveeks'a code
>
> 2. If a new user comes to any of the systers site like wiki,mailing list ,
> she registers so we  add an attribute in the form  of a openid url , the
> data gets store into the databse and for further use it will contact
> systers
> open id provider which will be redundant and restricted to be used with
> systers sites only.
>
> Suggestions are welcomed
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+mentor+unsubscribe at systers.org<systers-dev%2Bmentor%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=67&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to systers-dev+mentor at systers.org<systers-dev%2Bmentor at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>