[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kroupware
Subject:    Setup Converse.js XMPP plugin for roundcube
From:       Henning <henne.gwath () gmx ! de>
Date:       2014-04-12 14:59:30
Message-ID: 534954D2.8090903 () gmx ! de
[Download RAW message or body]

Hi,

next I tried to setup a chat environment using converse.js and punjab as
mentioned by Thomas in his blog post.
If I have punjab running (run by "twistd punjab") roundcubemail is not
reacting anymore. And I don't know how to stop the twistd service
(cannot find any process). The only way to get back control is to
disable the converse plugin in roundcube (config.inc.php) and close the
webmail session.

Did I miss something?

Henning

Am 12.04.2014 15:06, schrieb Henning:
> Thank's Chloé!
> 
> I again played around a bit with my config and got it working as I
> wanted, now sharing the settings:
> 
> ... SNIP ...
> 
> {mod_shared_roster_ldap,[
>     {ldap_base, "dc=domain,dc=eu"},
>     {ldap_filter, ""},
>     {ldap_user_cache_validity, 7200},
>     {ldap_group_cache_validity, 7200},
>     {ldap_auth_check, off},
>     {ldap_rfilter,
> "(&(objectClass=inetorgperson)(objectclass=AuthorizedServiceObject))"},
>     {ldap_groupattr, "objectclass"},
>     {ldap_useruid, "uid"},
>     {ldap_ufilter, "(uid=%u)"},
>     {ldap_groupdesc, "ou"},
>     {ldap_userdesc, "cn"}
>    ]},
> 
>   {mod_vcard_ldap, [
> 
> ... SNIP ...
> 
> 
> Next will be to add XMPP-support to roundcubemail.
> 
> regards,
> Henning
> 
> Am 10.04.2014 11:30, schrieb Chloé Desoutter:
>> Le 10/04/2014 10:21, Henning a écrit :
>>> Hi!
>>>
>>> Okay, I see I forgot to specify my question: authentication against ldap
>>> is not the problem. But how to get all users in a "shared roster", so
>>> everyone is able to see everyone else without having to manually add
>>> users to their contact-list?
>>>
>>> That is not that easy with ldap and recent ejabberd versions, as you
>>> cannot just use the mod_shared_roster module (I think).
>>>
>>> In the past it worked with just the
>>>
>>> {mod_shared_roster,[]}
>>>
>>> module, but it seems not to work anymore...
>>>
>>> The config section I use now is
>>>
>>>    {mod_shared_roster_ldap,[
>>>          {ldap_base, "dc=domain,dc=eu"},
>>>          {ldap_rfilter, "(objectClass=posixGroup)"},
>>>          {ldap_filter, ""},
>>>          %{ldap_groupattr, "cn"},
>>>          {ldap_gfilter,
>>> "(&(objectClass=posixGroup)(cn=POSIXGROUPNAME))"},
>>>          {ldap_groupdesc, "description"},
>>>          %{ldap_memberattr, "memberUid"},
>>>          %{ldap_memberattr_format, "cn=%u,ou=People,dc=domain,dc=eu"},
>>>          {ldap_ufilter,
>>> "(&(objectClass=inetOrgPerson)(objectClass=authorizedServiceObject)(uid=%u))"},
>>>
>>>          {ldap_useruid, "uid"},
>>>          {ldap_userdesc, "cn"}
>>>    ]},
>>>
>>>
>>
>> Hey,
>>
>> Here's my conf.
>>
>>   {mod_shared_roster_ldap,[
>>     {ldap_user_cache_validity, 7200},
>>     {ldap_group_cache_validity, 7200},
>>     {ldap_auth_check, off},
>>     {ldap_memberattr_format, "%u@atasta.net"},
>>     {ldap_memberattr, "mail"},
>>     {ldap_useruid, "uid"},
>>     {ldap_filter, "(objectClass=kolabinetorgperson)"}
>>     {ldap_rfilter, "(objectClass=kolabinetorgperson)"},
>>     {ldap_groupattr, "o"},
>>     {ldap_groupdesc, "o"},
>>     {ldap_userdesc, "cn"}
>>    ]},
>>
>> This way I split users by groups, these groups being the different
>> organizations of our company.
>>
>> HtH.
>>
>> Yours sincerely,
>>
>>
>>
>> _______________________________________________
>> users mailing list
>> users@lists.kolab.org
>> https://lists.kolab.org/mailman/listinfo/users
>>
> _______________________________________________
> users mailing list
> users@lists.kolab.org
> https://lists.kolab.org/mailman/listinfo/users
> 
_______________________________________________
users mailing list
users@lists.kolab.org
https://lists.kolab.org/mailman/listinfo/users
[prev in list] [next in list] [prev in thread] [next in thread]