Common Roster for all users?

Hi all,

I'm setting up a jabber server to serve as the central hub for all our
internal IM communications. I'm looking for a GPL'd solution that
allows me to do one simple thing: specify a common roster for all
users (that pretty much includes everyone in the company).

Now, with jabberd2, it doesn't seem like this is trivially possible -
it seems like I might be able to do this by preloading the
roster-items table with all combinations of all users, pre-authorized,
and resetting this every night.

Could ejabberd help make this simpler? Or am I just barking up the
wrong tree - perhaps no jabber-based IM solution will allow me to
effectively implement this system.

Thanks in advance for all your responses.

--

-- 
Sam Sgro
sam <at> spidersilk.net

Re: Common Roster for all users?

I think this is a pretty typical need in a corporate environment.  We're
running ejabberd here, and I ended up making an interface on our staff
portal that lets users bulk-add other users from our AD.  It works
decently well, but sending a pre-built roster would be ideal.
Unfortunately I'm still learning Erlang and don't understand it well
enough to implement this feature.

On Wed, 2004-12-01 at 22:56 -0500, Sam Sgro wrote:
> Hi all,
> 
> I'm setting up a jabber server to serve as the central hub for all our
> internal IM communications. I'm looking for a GPL'd solution that
> allows me to do one simple thing: specify a common roster for all
> users (that pretty much includes everyone in the company).
> 
> Now, with jabberd2, it doesn't seem like this is trivially possible -
> it seems like I might be able to do this by preloading the
> roster-items table with all combinations of all users, pre-authorized,
> and resetting this every night.
> 
> Could ejabberd help make this simpler? Or am I just barking up the
> wrong tree - perhaps no jabber-based IM solution will allow me to
> effectively implement this system.
> 
> Thanks in advance for all your responses.
> 

_______________________________________________
ejabberd mailing list

Ability to use any ldap account with no password

Hello, All!

I installed ejabberd-0.7.5 (Linux Red Hat 9) with {auth_method, ldap}.

LDAP-service - Lotus Domino 5.0.12 (for Linux).

And I use JAJC jabber-client (for Windows, version 0.0.8.112).

If I check the "Use plain text password" box when Tools -> Accounts ->
Setup, then ejabberd accept ONLY VALID ldap user's password.

If I DON'T check the "Use plain text password" box, then ejabberd
accept ANY (even empty) PASSWORD for any ldap user and after it I can
use jabber-service without problem!

Other clients (PSI, Expodus) permit to enter only valid ldap user's
password.

Is this issue with ejabberd, Lotus Domino LDAP-service or JAJC?

Thanks.
Kivel Oleg.

Re: Ability to use any ldap account with no password

Oleg Kivel wrote:
> Hello, All!
> 
> I installed ejabberd-0.7.5 (Linux Red Hat 9) with {auth_method, ldap}.
> 
> LDAP-service - Lotus Domino 5.0.12 (for Linux).
> 
> And I use JAJC jabber-client (for Windows, version 0.0.8.112).
> 
> If I check the "Use plain text password" box when Tools -> Accounts ->
> Setup, then ejabberd accept ONLY VALID ldap user's password.
> 
> If I DON'T check the "Use plain text password" box, then ejabberd
> accept ANY (even empty) PASSWORD for any ldap user and after it I can
> use jabber-service without problem!
> 
> Other clients (PSI, Expodus) permit to enter only valid ldap user's
> password.
> 
> Is this issue with ejabberd, Lotus Domino LDAP-service or JAJC?
> 

It may be an issue with clients. The correct way IS to use plain text
passwords (I suggest you use tls for your jabber client connections).
It may be that other clients use plaintext per default...

	MVH leifj

Re: Common Roster for all users?

Op donderdag 2 december 2004 07:27, schreef Steve Kondik:
> I think this is a pretty typical need in a corporate environment.  We're
> running ejabberd here, and I ended up making an interface on our staff
> portal that lets users bulk-add other users from our AD.  It works
> decently well, but sending a pre-built roster would be ideal.
> Unfortunately I'm still learning Erlang and don't understand it well
> enough to implement this feature.

Maybe useful:
<http://www.jabber.org/wiki/index.php/Shared Roster Groups>

--

-- 
Mvg, Sander Devrieze.

xmpp:sander <at> l4l.be ( http://jabber.l4l.be/ )

_______________________________________________
ejabberd mailing list
ejabberd <at> jabber.ru
http://lists.jabber.ru/mailman/listinfo/ejabberd

Re: Ability to use any ldap account with no password

>> I installed ejabberd-0.7.5 (Linux Red Hat 9) with {auth_method, ldap}.
>>
>> If I DON'T check the "Use plain text password" box, then ejabberd
>> accept ANY (even empty) PASSWORD for any ldap user and after it I can
>> use jabber-service without problem!
>> 
>> Other clients (PSI, Expodus) permit to enter only valid ldap user's
>> password.
>> 
>> Is this issue with ejabberd, Lotus Domino LDAP-service or JAJC?
>> 

LJ> It may be an issue with clients. The correct way IS to use plain text
LJ> passwords (I suggest you use tls for your jabber client connections).
LJ> It may be that other clients use plaintext per default...

LJ>         MVH leifj

But why does ejabberd permit unauthorized access anyway? What will be
if bad guy decide to use JAJC without "Use plain text password"?

Kivel Oleg.

icq gateway

  Hi!

  I install jabberd2 on RHAS3
  I install also JUD, mu-conference and pyICQ-t.
  JUD and conference works fine, but pyICQ-t don't work, because it
  use direct connection to login.icq.com server.
  Is it possible to use proxy connection for him?

--

-- 
Best regards,
 Dmitry                          mailto:dimit <at> narod.ru

Re: Ability to use any ldap account with no password

Oleg Kivel wrote:
>>>I installed ejabberd-0.7.5 (Linux Red Hat 9) with {auth_method, ldap}.
>>>
>>>If I DON'T check the "Use plain text password" box, then ejabberd
>>>accept ANY (even empty) PASSWORD for any ldap user and after it I can
>>>use jabber-service without problem!
>>>
>>>Other clients (PSI, Expodus) permit to enter only valid ldap user's
>>>password.
>>>
>>>Is this issue with ejabberd, Lotus Domino LDAP-service or JAJC?
>>>
> 
> 
> LJ> It may be an issue with clients. The correct way IS to use plain text
> LJ> passwords (I suggest you use tls for your jabber client connections).
> LJ> It may be that other clients use plaintext per default...
> 
> LJ>         MVH leifj
> 
> 
> But why does ejabberd permit unauthorized access anyway? What will be
> if bad guy decide to use JAJC without "Use plain text password"?

Plaintext passwords as opposed to legacy jabber shared-secret passwords.
None of these are 'unauthenticated'. Use of plaintext passwords wo tls
is not recommended but it's still not unauthenticated.

	MVH leifj

Re: icq gateway

Hello Dmitry,

Thursday, December 2, 2004, 2:53:30 PM, you wrote:

D>   Hi!

D>   I install jabberd2 on RHAS3
D>   I install also JUD, mu-conference and pyICQ-t.
D>   JUD and conference works fine, but pyICQ-t don't work, because it
D>   use direct connection to login.icq.com server.
D>   Is it possible to use proxy connection for him?

  Sorry, it was wrong mailing list :(

--

-- 
Best regards,
dmitry                            dimit(at)narod.ru

erlang jabber client library

Is anyone aware of any jabber client libraries written in erlang?