Ticket #7 (assigned enhancement)

Opened 5 years ago

Last modified 2 years ago

LDAP Support

Reported by: jelmer Owned by: jelmer
Priority: wishlist Milestone: 1.2.x
Component: BitlBee Version: devel
Keywords: Cc:
IRC client+version: Client-independent Operating System: Public server
OS version/distro:

Description

It would be nice to be able to store user data (buddy name -> nickname mappings, account data) on an LDAP database. This would particularly be useful for sharing data between various public servers.

Attachments

Change History

Changed 5 years ago by wilmer

  • type changed from defect to enhancement

Changed 5 years ago by wilmer

  • component changed from irc to bitlbee

Changed 5 years ago by jelmer

  • owner set to jelmer
  • status changed from new to assigned

I'd like to work on LDAP support, so assigning to me.

Changed 5 years ago by jelmer

  • milestone set to 2.0?

Changed 5 years ago by jelmer

  • milestone changed from 2.0? to 1.1?

Changed 5 years ago by wilmer

1.1 should probably have some nice configuration storage backend, so we can implement this and #23 at once in a nice and clean way.

Changed 5 years ago by jelmer

I've put a branch up at  http://jelmer.vernstok.nl/oss/bitlbee/bzr/storage/ that adds an abstraction layer for the storage support (and contains just one backend at the moment, which reads and writes the old BitlBee data files). Once this is merged into mainline, I'll have a look at LDAP support.

Changed 5 years ago by wilmer

Just read the diffs, looks good!

BTW, maybe it could be nice to allow multiple storages to be used for at least loading settings, this could be convenient for conversion from the old format to the (planned) new file format. And maybe also for migration from the usual files to LDAP.

For saving, one storage backend should be enough.

Changed 5 years ago by jelmer

right, that makes sense. This is quite easy to implement, but I'm a bit doubtful as to what the easiest way to configure such a thing would be. Adding a 'storage_migrate' option that specifies a storage backend to migrate from would make most sense to me. One of the things to keep in mind is that a smooth upgrade (without any required interference from the user) would be nice to have and should be possible. What do you think?

Changed 5 years ago by jelmer

Wilmer just merged some changes that add a 'account storage' and a 'account storage migrate' option. Left now is the actual LDAP backend, preferably in storage_ldap.c

Changed 4 years ago by jelmer

I'm currently stuck waiting for an OID assignment from IANA so I can fill those into the schema.

Changed 4 years ago by jelmer

Ok, we've been allocated an OID by IANA: 25873

Changed 3 years ago by wilmer

Changed 3 years ago by wilmer

  • milestone changed from 1.2 to 1.2.x

I'm trying out a feature freeze, I only want to fix bugs for the 1.2 release and postpone actual features until a later release.

Changed 2 years ago by wilmer

For the record, this is probably going to be merged in some near future. Some changes have to be made though, most of all we need a more atomic way of saving settings. This is a little bit complicated in LDAP because it'd be nice to avoid having to recreate the whole tree for a user every time we're saving settings.

Add/Change #7 (LDAP Support)

Author


E-mail address and user name can be saved in the Preferences.


Action
as assigned
 
Note: See TracTickets for help on using tickets.