Hello, is there a possibility to force disconnect user? I see only ejabberctl command unregister user, but not disconnect user, or disable user, or ban user for some time period.
So maybe suggestion for new version 3.0 ... possibility to disconnect user, disable user without deleting his accout(just freeze account), and ban user for time period.
And when I mention new version 3 of ejabberd...it will be wonderfull if we have more usable admin interface. Actualy...for bigger instalation is actual admin interface quite unfreindly.
Looking for ejabberd docs?
To access the most up-to-date ejabberd documentation, please visit docs.ejabberd.im »
Force disconnect user
Submitted by SasaXmmp on Thu, 2010-09-30 07:00
SasaXmmp wrote: I see only
I see only ejabberctl command unregister user, but not disconnect user, or disable user, or ban user for some time period.
In the ejabberd-modules SVN (see http://www.ejabberd.im/ejabberd-modules ) you will find mod_admin_extra. It provides additional commands like kick_session and ban_account.
it will be wonderfull if we have more usable admin interface. Actualy...for bigger instalation is actual admin interface quite unfreindly.
ejabberd's Web Admin gets minor improvements and some new features in each new release. It may look to you like old-fashioned, static, web 1.0. But it is not planed to receive major cosmetic changes, because Web Admin works, it works fast, it does what it has to do, and it is simple to develop.
thx for reply. I will try
thx for reply.
I will try that module, but why is not such a basic fuctionality in ejabberd core?
About web interface...I dont really ment some flashy, overcolor web 9.0 pages. Im just trying to deploy large installation of ejabberd and I found actual admin interface very unfriendly for that task. Looks like its designed for small installation with few users, and for large deployment autors expects another auth-source like ldap etc. Well this couldnt by a default case for everyone.
So, there is some proposals for web admin in ejab 3.0:
1. It surely can stay on web 1.0, we need functionality, no overcolor toy.
2. On user pages should be everything which is connected to user...as assignment to shared groups, extendet features like possibility to disable,ban,ban for time limit, also icon for immidiate disconnecting user will be fine.
3. Looks like inteface was design for small resolution, there is planty space, which could be used.
4. Managing shared roster groups is task for patience joga master, not for mortals...again planty of unused space.
5. possibility disabling entire virtual hosts or shared groups...so I wouldnt by forced manualy disabled all users in their account settings.
Next...you should build some heavily used modules to ejab core, because many users must deal with their nofriendly installation and someone can say that they providing some basic functionality, which one can expected from such a software....well there is more things, but I cant remember now.
So this is my findings after few months of administering ejabberd and I thing Im not alone with this findings? Anybody else?