I work as Unix Admin at a student run division of my university's IT department. Currently, I have jabberd2 running on a FreeBSD server. After doing some reading, I'm almost certainly going to jump ships to ejabberd, as soon as FreeBSD updates their net-im/ejabberd port (currently on 1.1.4).
Here is the basic setup: users authenticate against active directory but I'd also like a local authentication as well for pseudo users (I want to develop some applications with a jabber client connection). Having a shared roster would be nice, but many users don't like having everybody separated in groups. Currently, I let them chose how to have buddies organized and I run some MySQL scripts. The problem with this is that every semester if people don't go to the page and run the script, they get out of date (positions/locations changes.
All of our employee info is kept in a MSSQL database, so I think I could also use this for vcards/rosters, but I would have to heavily modify the MSSQL plugin to work with our schema.
To add more complication, I've discovered it may be possible for me to get the SRV record for jabber ports for wsu.edu, and thus to make this service university wide. I could either come up with a creative SQL solution, or if jabberd supports it, have multiple roster backends. Or maybe I could have multiple virtual hosts?
Can ejabberd make my XMPP dreams come true? Sorry for all the rambling, I'm just trying to get what naive ideas I have out there, and hope someone can translate them into an ejabberd based solutions.
Thanks a lot.
