Re: [Gaim-cabal] pidgin.im jabber server questions

[Daniel A. <dan...@gm...>]

On 10/22/06, Etan Reisner <de...@ed...> wrote:
> What authentication system do we want this to use? (This goes in hand
> with the open registration bit, we (more or less) need to use the
> internal database if we want open registration, but if we don't we can
> have it look at just about anywhere else we want, ldap, mysql, pam, etc.
> The ldap and mysql/obdc support is built in, for pam we'd have to use an
> auth module I wrote at Rutgers.)

While we're on the subject of authentication, we should talk about
Trac authentication.

In talking to Luke, he came up with the very reasonable requirement
that users must be registered in order to file bugs and other tickets.

I have a very basic Trac environment set up at http://pidgin.im/trac.

Trac is pretty configurable as far as permissions go - they are pretty granular:
http://pidgin.im/trac/wiki/TracPermissions

Trac can use any of the Apache2 based authentications We're using
httpd 2.0 and unfortunately, the authentication wasn't de-suckified
until 2.2 (where the Authentication method (Basic or Digest) was
separated out from the "Authentication Provider" (file, DBM, LDAP,
etc).

I think this means that we're stuck with Basic authentication because
we're going to need to dynamically add users.  The question then is
what do we want to as the auth. provider?  If we're not planning to
offer open jabber registration, then it probably doesn't make sense
that Trac auth is related to that.  On the other hand, we probably
don't want to be maintaining several different auth providers.   What
are you guys' thoughts?

We also have to deal with the various other decisions in the
configuration of Trac; some of these are going to be dependent on the
L&F of the new website.

Take a look and think about it.

-D