Thanks for the help. I was wondering if I needed remove from the cache also. I am now
removing from subscriber and xcap table just to make sure that the database does not
contain stale data.
Krish Kura
On Fri, Sep 30, 2011 at 3:01 AM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,
just to add that besides having the records in xcap table, if the
user is removed, it should have no access to it because it will be
authenticated for that. But since there is no record in subscriber
table anymore, the authentication will fail always. So besides
taking harddrive space, it is no impact in SIP side. IIRC, siremis
has a web interface for xcap, but also the delete operation has to
be done manually.
Cheers,
Daniel
On 9/28/11 4:10 PM, Peter Dunkley wrote:
Hello,
You don't need to worry about the contents of the presentity,
watcher, and active watcher tables. Entries in these tables will
be deleted if the user un-subscribes or logs out properly, and
failing that automatically cleaned up when the records themselves
expire.
When you remove a user you probably should remove any documents
belonging to them in xcap. At the moment this is a manual process
and not tied into the kamctl command.
Regards,
Peter
On Tue, 2011-09-27 at 13:49 -0500, Krishna Kurapati wrote:
Hi,
When a user is removed using "kamctl rm",
is there way way to clean up presence information
in the database (xcap, presentity,
watcher and active watcher tables) and in the cache? Is there a
event that gets fired when the user is
removed from subscriber table which I could handle in config